Re: Re: Rethink CS for require_once?

Andrew Nagy wrote:

I don't know if this has been discussed before, but what about using just require for internal packages and require_once for external? Rasmus Lerdorf mentioned at a PHP conference that require_once is really slow and should be avoided at all costs.

That with speed is nothing compared to other means needed... As Greg meant: everything is protected because it's coming and should ONLY come from require_once 'PEAR/base_package'; then in base_package require or require_once should be the same (in what concern internal private sub requirements, external should allways say require_once) -- bertrand Gugger (toggg)