On Thursday 18 June 2026 08:55:10 (+02:00), Jorg Sowa wrote:
> Thanks for all opinions. I will apply all changes in coming days to the
RFC
> content.
>
> > Is there a practical, real-world issue this solves?
>
> Portability of the autoloading. I had a case in the past where my
wrongly
> cased namespace didn't cause any problem locally, but it failed in the
> production because of different OS. This is real world-issue.
>
Well, not in PHP AFAIK.
SPL class autoloading was designed under portability
principles and properly vetted in this regard, from top
of my head since it's incarnation in PHP 5.1.
So I'd be highly interested where PHP's standard class
autoloading has this "real world-issue" in its collation.
E.g. did you use a specific PHP script to generate the
dynamic include instructions?
Or were those templated by some specific PHP script, or
were you implementing or inheriting a specific framework
that makes use of PHP scripts etc. that undermined
standard stability and portability principles in software
and system design?
More context warmheartly appreceated.
Best,
--hakre
