Databases
StackOverflow2013
Postsdbo
POScoped using-directive within a struct/class declaration?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POScoped using-directive within a struct/class declaration?
    primarykey
    data
    text
    <p>I find that my C++ <em>header files</em> are quite hard to read (and really tedious to type) with all the fully-qualified types (which goes as deep as 4 nested namespaces). This is the question (all the answers give messy alternatives to implementing it, but that's <em>not</em> the question): <strong><em>Is there a strong reason against introducing scoped using-directive in structs and classes in the C++ language</em></strong> (while it's permissible to have scoped using-declaration in functions)?</p> <p>e.g.</p> <pre><code>class Foo : public Bar { using namespace System; using namespace System::Network; using namespace System::Network::Win32::Sockets; using Bar::MemberFunc; // no conflict with this // e.g. of how messy my header files are without scoped using-directive void FooBar(System::Network::Win32::Sockets::Handle handle, System::Network::Win32::Sockets::Error&amp; error /*, more fully-qualified param declarations... */); }; </code></pre> <p>Since <code>namespace</code> is a keyword, I would've thought it's distinct enough to cause no conflict with the scoped using declaration such as <code>Bar::MemberFunc</code>.</p> <p>EDIT: Read the question carefully ---> I've bolded it. Reminder: we're <strong>not</strong> discussing how to improve readability of the example here. Suggesting how scoped using-directive could be implemented (i.e. by means of adding keywords / constructs etc.) in the C++ language is <em>NOT</em> an answer (if you could find an elegant way to implement this using existing C++ language standards, then it would of course be an answer)!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStaskinoor
    1. USZach Saw
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POScoped using-directive within a struct/class declaration?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POScoped using-directive within a struct/class declaration?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POScoped using-directive within a struct/class declaration?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPersonally, I think it's a sign of bad design when there are so many nested namespaces.
      singulars
      1. POScoped using-directive within a struct/class declaration?
      1. USOmnifarious
    2. COBy your reasoning, the .NET framework would be a bad design.
      singulars
      1. POScoped using-directive within a struct/class declaration?
      1. USZach Saw
    3. CO@Zach Saw - It's bad C++ design, it's not-so-great Java design and it's OK (but still not fantastic) Python design. And if the .NET framework for C++ does that, then yes, it's not very well designed. I do think though that C++ could use a mechanism like you suggested for restricting the scope of a using declaration. That would cause heavily nested namespaces to be a less bad design in C++ than they currently are.
      singulars
      1. POScoped using-directive within a struct/class declaration?
      1. USOmnifarious
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload