Tom Schindl wrote: [...]
It doesn't matter to me. If you prefer to have:
* obj: $socket * arg1: $len
I'd also prefer to have it this way. How does this look like for static methods?
* class: APR::SOCKET * arg1: $len
You mean for something like:
Apache->warn(@msg);
you suggest to have:
class: Apache arg1: @msg
correct? Though it can be $r->warn(@msg) just as well. (Please disregard for a moment that Apache::Log is a big mess, which we need to rectify). Another example would be Apache->request().
Why could you not leave the obj/class. You would not state the obj/class for any other object oriented language like e.g. java, when using objects this is implied, isn't it? Normally one only marks methods to be static/instance and private/protected/public.
Sorry, I'm not following you here, Tom. What are you suggesting again?
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
