Re: Re: Not autoloading functions

> > > The problem with stop-gap measures is they become entrenched, and the > proper solution doesn't get implemented > > This would be my general point of view - unfortunately, functions are > essentially useless at present, in a world with Composer, unless you're > willing to preload all functions from all packages up-front. > > The only suggested solutions I've heard for the name resolution issue with > function autoloading frankly are all horrible - much worse than this simple > alternative. > > Add to that the fact that likely 90% of all functions in the wild (at least > in Composer packages) are currently implemented as public static functions, > and in my opinion, this is starting to sound less like a stop-gap and more > like a simple solution to a problem we've been solving with a stop-gap for, > oh, 10 years or so... Again, if you choose to use static methods instead of functions, why do you need this special syntax for calling them then? Regards, Niklas