Re: Re: Scoping of "use" statements and a strategy for 5.3/6.0 release of namespace

Stan Vassilev | FM wrote: >> Stan Vassilev | FM wrote: >>> Hi, >>> >>> Multiple namespaces per file were introduced to allow certain >>> workflows in PEAR and frameworks like Symphony which can combine >>> multiple classes and namespaces in a single package. >>> >>> They work like this: >>> >>> >>> namespace X; >>> >>> ... >>> >>> namespace Y; >>> >>> ... >>> >>> >>> The problem is, no one thought of scoping "use" statements, so now >>> those merged files share their "use" imports, thus breaking all the >>> code where collisions occur. >> >> Hi, >> >> Stan, did you actually try this out? According to my checkout of CVS, >> you're wrong. Try this script: >> > > What's the logic behind namespace declaration affecting file-level > import statements. Looks like such a hack to me. ??? I'm confused. First you say that merged files share "use" imports, which is not true, then complain that namespace declaration affects file-level import statements. Which one is the problem? Greg Greg