Databases
StackOverflow2013
Postsdbo
PONamespace + functions versus static methods on a class
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONamespace + functions versus static methods on a class
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USStephen Canon
    1. USRobertL
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    3. PL
      singulars
      1. LTLinked
    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. PONamespace + functions versus static methods on a class
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONamespace + functions versus static methods on a class
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PONamespace + functions versus static methods on a class
      1. This table or related slice is empty.
      1. VTUpMod
    1. COfor one thing, namespaces are more recent addition to the language, compared to classes and static methods, which were in the language from the time it was called "C with classes". Some programmers may be more comfortable with older features. Some other programmers may be using old compilers. Just my $.02
      singulars
      1. PONamespace + functions versus static methods on a class
      1. USRom
    2. CO@Rom: You're right about "old programmers", but wrong about "old compilers". Namespaces are correctly compiled since eons (I worked with them with Visual C++ 6, dating from 1998!). As for the "C with classes", some people in this forum weren't even born when that happened: Using this as an argument to avoid a standard and widespread C++ feature is a fallacy. In conclusion, only obsolete C++ compilers don't support namespaces. Don't use that argument as an excuse to not use them.
      singulars
      1. PONamespace + functions versus static methods on a class
      1. USpaercebal
    3. CO@paercebal: some ancient compilers are still in use in embedded world. Not supporting namespaces is probably one of the smallest inconveniences one needs to put up with while writing code for various small CPUs which everyone interacts with every day: your stereo, your microwave, engine control unit in your car, traffic light, etc. Just to be clear: I'm not advocating for not using a better, newer compilers everywhere. Au conrare: I'm all for newest language features (except RTTI ;) ). I'm just pointing out that such a tendency exists
      singulars
      1. PONamespace + functions versus static methods on a class
      1. USRom
 

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