Re: solving the namespace conflict issues betweenfunction/staticmethod class constant/ns constant

On Mon, Sep 29, 2008 at 8:36 PM, Daniel Convissor <danielc@analysisandsolutions.com> wrote: > Hi Greg: > > On Sun, Sep 28, 2008 at 09:58:25PM -0500, Gregory Beaver wrote: >> >> The second highest vote was :::, but there was strong objection to this >> as well from some. > > Sounds like you have the tally or know where it is (or you have an > excellent memory). Do you have a URI for it, please? > > Regardless of opposition, it did get the second highest vote count, so > has support from several people. > > > >> The problem, I still believe, is that we are focused >> on having the same:::stupid:::operator:::between:::everything. > ... >> In truth, it will be a lot easier to debug code if this is a different >> separator, as the boundary between namespace and element will be crystal >> clear. For instance: > ... >> my::framework..someFunction()->aProperty->someMethod(); > > Good points. And thanks for the patch. (Perhaps we can harness the vast > amounts of energy inside Greg to resolve our oil dependence?) > > Regardless of whether we use the same separator between > namespaces and the elements or if we just use a different separator > between namespaces and the elements, some separator needs to change. I always liked ~ use some~long~namespace; some~long~namespace~class::function(); some~namespace~function(); some~namespace~$var; new ~ArrayIterator(); Keep up the good work everyone--I'm really looking forward to 5.3. I've already started using the alpha.