I'm not sure I understand this problem. Isn't it doable to define
defines at runtime and then put them under a certain namespace? I'm
assuming namespaces are defined before defines?
Ideally, I'd say there should be no code limitations inside namespaces.
But if this poses technical problems. Th
Matthias,
Simply put, const != define. Like I think Sara mentioned before, defines are
runtime-defined, and making it both compile-time/runtime defined based on
context will be really confusing.
Also, I'm not accepting variables in namespaces and this is not needed
either. So, yes, this is outsid
MB>>work that is worth nothing you should simply try to come up with a working
MB>>patch using a working separator which can clearly only be "\".
That's one creative way of using "working", "clearly" and "only" with
meanings that I was not familiar with before. :)
--
Stanislav Malyshev, Zend Pr
Hello Jessie,
i already showed that dropping constants in namespaces leeds to static
classes or private classes. So we are just shifting here. Instead of doing
work that is worth nothing you should simply try to come up with a working
patch using a working separator which can clearly only be "\"
