Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The way you did it seems to me the correct way to do it, if you're going to do it at all. Because the expansion of the macro is <em>so</em> similar to what you'd expect[1], I think it's valid to make the macro look like syntax (), rather than the usually recommended SCARY_UPPERCASE_MACROS() which are used to show that this code doesn't follow usual syntax and you should only use it carefully.</p> <p>[1] The only flaw being the inability to declare variables, which is unlikely anyway, and likely to produce an error in the right place when used incorrectly, rather than doing something weird.</p> <p>Furthermore, even small increases in readability are important, so being able to say <code>until (</code> instead of <code>while (!</code> really does make it easier to read many loops. If the ending condition is more easily thought of as an exceptional condition (regardless of whether it is or not) writing the loop that way round makes it easier to read. So even though it is only syntactic sugar, I think there's reason to consider it.</p> <p><em>However</em> I don't think it's worth it. The benefit is small, since most programmers are used to reading <code>if (!</code> and the cost is real: Anyone reading the code will have to check whether this a macro, or a custom compiler, and whether or no it does what they think. And it may misleadingly make you think you can do things like <code>i=5 unless xxxx;</code>. Such little improvements, if widespread, would fragment the language, so often it's best to do things the standard way, and adopt improvements slowly.</p> <p>However, it can be done well: the entirety of boost and tr1, especially the stuff done with templates to look like extensions to the library, involves extending C++ in various ways, many of which aren't adopted as they didn't seem worth it, but many of which have small or very widespread take-up because they made real improvements.</p>
    singulars
    1. This table or related slice is empty.
    1. POSyntactic sugar in C/C++
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USkay
    1. USJack V.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSyntactic sugar in C/C++
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe first paragraph of this answer is problematic, to say the least! Macros are not namespaced; they are totally global. So it is *terrible* to give them short names that might be used elsewhere. If you define a macro with a short name such as `until`, and then you include a 3rd party header which declares a member function `until`, that header will be broken. It will try to declare `void until(int a);` but instead will be saying `void while(!(int a));` Good luck deciphering that error message! And so (unsurprisingly) Boost uses scary uppercase names with prefixes for all its macro tricks.
      singulars
      1. PO
      1. USDaniel Earwicker
 

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