Search results

Jump to: navigation, search
  • Currently there is feature like "static global" in C or "unnamed namespace" in C++. Access specifiers for module-level symbols control access, not vis
    9 KB (1,251 words) - 21:39, 20 May 2015
  • | Add namespace scopes to support calling external C++ functions in C++ namespaces
    9 KB (1,188 words) - 22:34, 13 July 2016
  • ...oint of view, and has the additional advantage of not polluting the type's namespace:
    2 KB (250 words) - 23:34, 4 August 2016
  • namespace width
    4 KB (592 words) - 20:09, 9 March 2014
  • ...evel access specifiers make no sense to C++. However, there is an "unnamed namespace" feature, that forces internal linkage for a symbol: namespace
    8 KB (1,284 words) - 11:29, 15 February 2018
  • * Add a namespace gcc { namespace d { } } for common codegen routines.
    9 KB (1,306 words) - 20:04, 1 September 2015
  • What we have today, declaration of a C++ function, without namespace: string namespace (string namespace) { // mangle the namespace ... }
    14 KB (2,079 words) - 19:52, 1 September 2015
  • * we <code>import</code> a module instead of <code>using</code> a namespace;
    26 KB (3,437 words) - 23:54, 9 May 2021
  • * Namespace
    4 KB (519 words) - 12:49, 13 October 2013
  • !'''Add namespace scopes to support referencing external C++ symbols in C++ namespaces''' A namespace scope creates a scope with a name, and inside that scope all declarations b
    3 KB (453 words) - 06:07, 17 July 2014
  • // Namespace block, does *not* introduce any symbols on its own Binding C++ namespaces would no longer introduce the namespace as a symbol, leaving scoping to D's module system. Again, this is believed
    6 KB (868 words) - 05:49, 4 March 2018
  • // special modules named "_" group symbols from a namespace other than
    6 KB (918 words) - 17:05, 17 August 2019