# Autoglobal CVs without silence -- Summary

- Thread: https://externals.io/message/27689
- Original archive: https://news-web.php.net/php.internals/27689
- Started by Andi Gutmans on 2007-01-27T17:16:46+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #27689 — Andi Gutmans — 2007-01-27T17:16:46+00:00

URL: https://externals.io/message/27689#27689

Btw, for people who truly need the Unicode support I actually do think we might want to consider requiring them to fetch the input
variables through a new API and/or object. I don't think we need to make it seamless if the "default" behavior we provide (whatever
that ends up being) isn't good enough...

Andi 

> -----Original Message-----
> From: Andi Gutmans [mailto:andi@zend.com] 
> Sent: Saturday, January 27, 2007 9:15 AM
> To: 'Sara Golemon'; 'internals@lists.php.net'; 'Andrei 
> Zmievski'; 'Dmitry Stogov'
> Subject: RE: [PHP-DEV] Autoglobal CVs without silence -- Summary
> 
> Hi Sara,
> I don't feel to great with this patch. It kind of feels like 
> twisting the language implementation around for some very 
> specific problem which probably shouldn't be fixed at this 
> level. Andrei says performance of Unicode isn't great so it 
> shouldn't matter too much, but I think a) it's not only about 
> performance but also about maintainability. The code in PHP 6 
> is already much more complex than that of PHP 5 and has 
> become much harder to maintain. Such additional changes will 
> make it worse b) There will still be plenty of people who use 
> PHP 6 in PHP 5 mode.
> 
> I still haven't quite understood why not just do the 
> detection on the whole auto-global when it's being fetched 
> (or even during request startup). As Andrei said, it's slow 
> anyway so for people who need Unicode that should be an 
> affordable hit.
> 
> Maybe I don't understand the problem in enough detail and it 
> might make sense for me to talk to Andrei via voice directly, 
> but I really don't think we should be over eager commiting 
> this patch. It'll not be good for the engine long term (not 
> that I don't appreciate your efforts and hard work on this patch).
> 
> Andi 
> 
> > […]
> think about 
> > […]
> argument is 
> > […]
> runtime based 
> > […]
> auto global 
> > […]
> execution 
> > […]
> situations where 
> > […]
> timetable 
> > […]
> one side, 
> > […]
> by default", 
> > […]
> and expect 
> > […]
> unsubscribe, 
> > […]

---

## #27697 — Pierre — 2007-01-27T19:50:16+00:00

URL: https://externals.io/message/27689#27697 · In reply to: #27689

> Btw, for people who truly need the Unicode support I actually do think we might want to consider requiring them to fetch the input
> variables through a new API and/or object. I don't think we need to make it seamless if the "default" behavior we provide (whatever
> that ends up being) isn't good enough...

Amen. And know what? ext/filter provides all we need except the object
interface, but I promise to come with a proposal+patch for it as soon
as possible.

--Pierre