2002_10_04, [EMAIL PROTECTED] wrote: > Consider, if you will, any method whose arguments > are other instances of the same class
That's certainly something to look out for. However, if objects of your class (or any inherited class) are never going to be sensible candidates for arguments to the methods you want to 'proceduralize', then you may still be safe. Of course "never" is a hard thing to be certain about. In the CGI.pm case, I think the intent was that folks used to the procedural interface would have the option of using it and would never have to learn the OO interface. If they never learn the OO interface, then they probably won't be throwing many CGI objects around as potential arguments for anything. It may be that some folks have gone "halfway" and run into problems when the mix interfaces. I dunno. I'm an old stick in the mud who hasn't bothered to start using CGI.pm's OO interface :) -matt
