Kirby writes -

What I *don't* think any standard Java API is designed to accommodate is simple parameter switching, i.e. to catch (int a, int b) verus (int b, int a). Nor even (int a, float b) versus (float b, int a)

I don't pretend to know what is customary - but while int a, int b v. int b,int a won't fly I don't see why (int a, float b), (float b int a) wouldn't, and if it flies and helps - why not use it. But I agree with you in the sense that if I were in fact working in Java I would be less concerned about insulating a user from an API that might make argument order significant. The poor gal has to deal with a compile cycle, casting about of types, etc. and etc. in any case. They are programming, in the most formalistic sense of the word, whether they want to be or not. But in Python/VPython/PyGeo one is working in immediate mode. And when it comes to the point when a user is building geometric constructions by script, I would ideally like them to be thinking more as a geometer, then as a programmer. If 'them' is basically just me, it is no less true. Since there is no *geometric* reason for plane, line to be preferable over line, plane in finding an intersection, I would like there not to be an artificially imposed way it needs to be done. Basically just trying to get out of the way. Art