On Sat, 08 Sep 2001, Andi Gutmans wrote:
> Anyway, performance aside, there is also the point of conventions. Up to 
> now, PHP has been pretty much a functional language with an argument list. 
> It might make sense for big certificates to be passed as arrays. But 
> instead of going ahead and diving into the code, I think it'd be a good 
> idea if we came up with guidelines for the cases where it's OK to pass 
> arrays. IMO, it should be in very specific cases where it is clearly 
> beneficial to use arrays than passing 10 arguments. The guidelines should 
> also take performance into account and should only allow its usage in 
> functions where performance is not much of an issue.
> If we make it very clear it will be easy for PHP dev to shout "Hey, you're 
> not allowed to use this in function foo() because of a, b, c".
> I don't want to be a pain but I want to make sure we don't start a bad 
> status quo. From my experience, you make this kind of stuff available and 
> it gets misused very quickly.

The real solution to this, of course, would be keyword arguments. How
about them for v2?


"In My Egotistical Opinion, most people's C programs should be indented
six feet downward and covered with dirt." -- Blair P. Houghton

PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to