Databases
StackOverflow2013
Postsdbo
POHow can I cause the compiler to issue an error for classes that define the method body when using the __interface keyword?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I cause the compiler to issue an error for classes that define the method body when using the __interface keyword?
    primarykey
    data
    text
    <p>After reading this article: <a href="http://www.codeproject.com/KB/cpp/CppInterfaces.aspx" rel="nofollow">Using Interfaces in C++</a></p> <p>I have decided to use the <code>__interface</code> keyword with a macro that will add virtual destructors as described in the above link.</p> <p>I was happy that the <code>__interface</code> keyword will cause the compiler to enforce interface rules, but I was disappointed when I took it for a test drive... It turns out that the <code>__interface</code> keyword does not enforce the rule that a method in the interface should not contain a method body.</p> <p>I can of course add a macro for function methods but I don't want to do this. Does anyone have any other suggestions?</p> <p><strong>EDIT</strong>: portability is a none issue for me because i must compile on both windows and linux so i will use the <code>__interface</code> keyword when i'm on windows and not on linux , that will be in order to enforce the below rules , <strong>which can't be enforced via abstract base class</strong>: </p> <ol> <li>Can inherit from zero or more base interfaces.</li> <li>Can only contain public, pure virtual methods.</li> <li>Cannot contain data members; properties are allowed. </li> <li>Cannot inherit from a base class.</li> <li>Cannot contain constructors, destructors, or operators.</li> <li>Cannot contain static methods.</li> </ol> <p>besides the destructor issue which can be workaround one can see the advantage of using this keyword in windows env of course.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRobocide
    1. USRobocide
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow can I cause the compiler to issue an error for classes that define the method body when using the __interface keyword?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI agree with most commenters to that article you link to: this is simply macro abuse. If you are serious about enforcing restrictions on your interface classes, do that with a tool that parses the code (shouldn't be that hard, you only need to parse a small subset of the grammar and only well enough to check a few conditions). Otherwise, don't bother because you are simply trading one set of "programmer discipline" rules for another. I see no benefit in that.
      singulars
      1. POHow can I cause the compiler to issue an error for classes that define the method body when using the __interface keyword?
      1. USJon
    2. CO+1 Jon for your opinion, i will consider it, though i don't want to be depended on external tool to enforce interface restrictions.
      singulars
      1. POHow can I cause the compiler to issue an error for classes that define the method body when using the __interface keyword?
      1. USRobocide
    3. COC++ doesn't have tools to enforce a specific programming style. It allows you to do things the way you want, and it allows you to mix and match different styles. Some languages only support their "one true style", and doesn't have this "problem" that you can choose. If you don't want function bodies, just don't add them!
      singulars
      1. POHow can I cause the compiler to issue an error for classes that define the method body when using the __interface keyword?
      1. USBo Persson
 

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