
2 Jan
2010
2 Jan
'10
9:22 a.m.
Supporting replacing boost with a nested namespace easily gets very tricky without enforcing stricter coding conventions with explicit end-namespace tagging in boost. So I think allowing replacing boost with nested namespace is not worth it unless someone come up with a clever and simple way of making this work correctly.
I'd go so far as to say it's basically impossible with the current code base - I started out using regexes that matched nested { and } so I could identify the full boost namespace scope - but although it 99% worked there were always cases where there were { or } in macros or comments that weren't balanced :-( In short you would need a full C++ preprocessor and lexor to handle this. John.