Larry Garfield wrote:
> See, I'm working on a different approach for Drupal. We're actually scanning
> our own code base and building up an index of all classes (and functions!) in
> the system, saving that to the database, and then the autoload implementation
> just polls the database for the
On Thursday 03 April 2008, Colin Guthrie wrote:
> Larry Garfield wrote:
> > I believe the decision from -internals was "seriously, who uses static
> > methods and functions in the same code base that would use namespaces?"
> > Of course, I would hope to be able to say "me!" once I am able to upgr
Larry Garfield wrote:
> On Wednesday 02 April 2008, Jochem Maas wrote:
>
>>> there is one curiosity / caveat underlying the 5.3 implementation... so
>>> does the namespace get supplied to the autoload function as well as the
>>> class name? is it just one big string or are they separate?
>> one
Colin Guthrie wrote:
Ryan Panning wrote:
Your idea for replacing '::' with '/' is good but I'd think it'll
interfere with the arithmetic operator '/'. I'm sure they must have
discussed such options.
He didn't mean doing that in the code syntax, just in the autoload
function to convert it to a
Ryan Panning wrote:
> Richard Heyes wrote:
>>> err-um sorry for the noise; actually the namespaces work w/ functions
>>> as well.
>>
>> So not OO specific? Is there anything I can read that describes them?
>>
> Yes, it's on the docs site. Although this continues to change as I
> believe brackets {}
Ryan Panning wrote:
> Jochem Maas wrote:
>> essentially it boils down to replacing '::' with '/' to determine the
>> path
>> from the namespace in your case - that is easy enough, your still
>> stuck with
>> finding out whether your being asked to load a namespace, class, or
>> function
>> (do name
6 matches
Mail list logo
