> At 23:09 22-08-01, Andrei Zmievski wrote:
> >On Wed, 22 Aug 2001, Zeev Suraski wrote:
> > > How about phf_, for PHP Helper Function?
> > > I see a point in differentiating language level API functions (e.g.
> > > output buffering) and module-specific helper functions (e.g., like
> > > php_mysql_do_connect()).
> >Explain what the point is, then. I would assume that functions like
> >php_mysql_do_connect() are scoped statically, so it shouldn't be a big
> >deal that they have php_ prefix.
> It's not about possible symbol clashes...
Indeed, even when possible no two functions should have the same tail after
> When debugging (or when reading code), it helps to know what's a part of
> the API and what isn't. It also makes different types of prefix-based
> searching (e.g., gdb's completion, or emacs' search feature) a bit easier.
> Is it a big deal? No, but it can be useful and has no real drawbacks.
In my case, it is useful IMHO.
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]