You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The namespacesynopsis element is not very useful. It really should be a container for other declarations.
The use of "namespace" in the name is potentially confusing in an XML vocabulary where "namespace" is both common and means something else entirely.
Although some languages, like C++ and C#, call the container that is used for providing scoped names a "namespace", many languages call them something else. Java, Perl, and Python, for example, all call them "packages".
The word "package" is overloaded in computer software as well, but it's not so immediately confusing in an XML vocabulary.
The proposal is to recast the construct as a packagesynopsis and make it a container.
The text was updated successfully, but these errors were encountered:
The previous tag was based on a prerelease of DocBook 5.2, this patch
brings it to the current prerelease (which is highly unlikely to change
much).
The change was introduced in the specification following
docbook/docbook#223
Change-Id: I1abf388cdf9f8777dbf5e9e3f700a52334d5275d
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
At the last DocBook TC meeting, we concluded that
namespacesynopsis
element is not very useful. It really should be a container for other declarations.Although some languages, like C++ and C#, call the container that is used for providing scoped names a "namespace", many languages call them something else. Java, Perl, and Python, for example, all call them "packages".
The word "package" is overloaded in computer software as well, but it's not so immediately confusing in an XML vocabulary.
The proposal is to recast the construct as a
packagesynopsis
and make it a container.The text was updated successfully, but these errors were encountered: