Cart
[Home] [By Thread] [By Date] [Recent Entries]
Rich Salz <rsalz@d...> wrote: |> Namespaces should never have been scoped. That's a big part of what |> drove the implementation complexity up to such a large degree. | | But it's conceptually much cleaner. s/much/somewhat/ and then only maybe. | Who likes pascal style variable declarations at the top, isntead of | local scope rules? Even if it's easy to analogise element hierarchies into "block structure" there is no such thing as "local scope rules" without a lot of ancillary machinery. The reality is that scopes are nested, and resolution is always with respect to the innermost defining block, not the immediately "local" block. This implies that a proper resolution mechanism will have to maintain a stack of scoped definitions, which is where the complexity comes in. | It also makes component software easier, since I can just locally use a | "ds" prefix to indicate XML DSIG, without having to globally coordinate | with every part of a program working on a document. What if this prefix is already "taken" by an "outer block"? (Joe Engish's typology of "neurosis" and "psychosis" comes to mind.)
|
