C++ FAQ
/ Topics beginning with 'N'
Recent changes - 11 changed FAQs.
In a list,
or in a chain,
or here:
[4.1],
[4.2],
[6.3],
[6.12],
[10.3],
[15.22],
[27.15],
[35.13],
[35.14],
[35.15],
[39.6].
Translated into 16 languages.
English,
Belorussian / Minsk,
Bosnian / Serbian / Croatian,
Bulgarian,
Chinese (GB, Mainland),
Chinese (Big5, Taiwan),
French,
German,
Greek,
Korean,
Polish,
Portuguese,
Romanian,
Russian,
Spanish,
Turkish.
Mirrored in 11 countries.
USA,
France,
Germany,
Ireland,
Israel,
Italy,
Poland,
Portugal,
Spain,
Taiwan,
U.K..
|
C++ FAQ topics beginning with 'N'
[ A
| B
| C
| D
| E
| F
| G
| H
| I
| J
| K
| L
| M
| N
| O
| P
| Q
| R
| S
| T
| U
| V
| W
| X
| Y
| Z
]
- Naive/wrong beliefs
- Always name numeric literals ...
[29.11]
- Friendship breaks encapsulation ...
[14.2]
- inline functions always improve performance ...
[9.3]
- Methods always better than friend-functions ...
[15.9]
- Multi-line macros simply use {...} ...
[39.5]
- Never use #define ...
[29.7]
- Never use multiple-inheritance ...
[25.2],
[25.3]
- One size fits all ...
[25.6]
- protected data is evil ...
[19.8]
- "Always" and "Never" rules ...
[23.3]
- "Evil" things should never be used ...
[6.15]
- Software has rules that always apply ...
[6.16],
[17.8],
[21.8],
[23.4],
[25.5]
- There exists a purely technical definition of "good" ...
[6.17]
- Token-pasting doesn't require two levels of macros ...
[39.6]
- Name hiding ...
[23.9]
- NAME2() macro for token pasting ...
[39.6]
- Named Constructor Idiom ...
[10.8],
[16.21],
[16.24]
- Named Parameter Idiom ...
[10.20]
- Namespaces and using ...
[27.5]
- Naming numeric literals ...
[29.11]
- NaN: comparisons ...
[29.14]
- NaN: not a number ...
[29.15]
- NCITS ...
[6.13]
- Nested generalization ...
[25.5]
- Netiquette ...
[5]
- Acronyms ...
[5.1]
- Attachments: don't! ...
[5.4]
- From: line of a posting ...
[5.4]
- General netiquette ...
[5.4]
- Getting and reading other FAQs ...
[5.14]
- HTML postings: don't! ...
[5.4]
- Job ads ...
[5.10]
- Posting code ...
[5.8]
- Reply-To: line of a posting ...
[5.4]
- Response to off-topic postings ...
[5.12]
- Resumé postings ...
[5.11]
- Rich-text postings: don't! ...
[5.4]
- Selecting an appropriate newsgroup ...
[5.9]
- Spam ...
[5.13]
- Subject: line of a posting ...
[5.7]
- Top-post: don't! ...
[5.4]
- NETLIB, Collection of Numerical Algorithms ...
[29.17],
[37.7]
- new ...
[16],
[16.1]
- Advantages over malloc() ...
[16.4]
- Allocating an array with new T[n] ...
[16.11]
- Automatically freed on program exit ...
[10.16]
- Automating a NULL test ...
[16.7]
- Breaking it into pools ...
[11.14]
- Corruption — bang, you're dead ...
[16.12],
[30.3],
[38.7],
[38.8]
- delete and free() might use different heaps ...
[16.9],
[16.10]
- delete handles NULL automatically ...
[16.8]
- delete has two steps ...
[16.9]
- delete this ...
[16.15]
- delete[] uses magic ...
[16.14],
[38.7],
[38.8]
- delete[] vs. delete ...
[16.12]
- delete[] vs. delete for built-in types ...
[16.13],
[26.11]
- Deleting an array with delete[] ...
[16.11]
- Difference between delete and delete[] ...
[13.10],
[16.3],
[16.11]
- Garbage collectors ...
[16.26],
[16.27],
[16.28]
- Mixing malloc() and delete ...
[16.3]
- Mixing new and free() ...
[16.3]
- Mixing with free() ...
[16.3]
- Multi-dimensional arrays ...
[16.16],
[16.17]
- new and malloc() might use different heaps ...
[16.5]
- new has two steps ...
[16.10]
- new never returns NULL ...
[16.6]
- Placement new ...
[16.10]
- Placement new doesn't allocate ...
[11.10]
- Prohibiting local objects ...
[16.21]
- realloc() ...
[16.5]
- Reference counting ...
[16.22],
[16.23],
[16.24],
[16.25]
- Runtime costs of ...
[31.2],
[31.4],
[31.5]
- std::bad_alloc ...
[16.6],
[16.7]
- std::set_new_handler ...
[16.7]
- Use std::auto_ptr only when pointing into the heap ...
[23.6]
- Why use new rather than malloc() ...
[16.4]
- New handler ...
[16.7]
- new keyword ...
[16.1],
[16.4],
[16.5],
[16.11]
- new: might use different heap from malloc() ...
[16.5]
- Newbie questions / answers ...
[29]
- Newlines: whitespace standards ...
[29.10]
- Newsgroups
- comp.graphics ...
[5.9]
- comp.lang.c ...
[5.9]
- comp.lang.c++ ...
[5.9]
- comp.lang.c++.moderated ...
[5.9]
- comp.object ...
[5.9]
- comp.os.ms-windows.programmer.misc ...
[5.9]
- comp.os.ms-windows.programmer.tools.* ...
[5.9]
- comp.os.msdos.programmer ...
[5.9],
[40.5]
- comp.os.msdos.programmer.turbovision ...
[5.9]
- comp.programming ...
[5.9]
- comp.sources.wanted ...
[5.9]
- comp.std.c++ ...
[5.9]
- comp.sys.mac.oop.* ...
[5.9]
- comp.sys.mac.programmer.* ...
[5.9]
- comp.unix.programmer ...
[5.9],
[40.5]
- comp.unix.solaris ...
[5.9]
- comp.windows.ms.programmer ...
[40.5]
- gnu.g++.bug ...
[5.9]
- gnu.g++.help ...
[5.9]
- NIHCL (National Institute of Heath Class Library) ...
[37.6]
- No inheritance, no pointers, Serialization and ...
[36.7]
- No Warranty ...
[1.4]
- Nodes within graphs (definition), Serialization and ...
[36.13]
- noecho() ...
[15.18]
- Non-abstract functions ...
[20.6]
- Non-human-readable format mechanics, Serialization and ...
[36.6]
- Non-human-readable format tradeoffs, Serialization and ...
[36.3]
- Non-member functions: inline ...
[9.6]
- Non-pure virtual functions ...
[20.6]
- Non-virtual
- Calling a virtual ...
[23.1],
[23.2]
- Public Overloaded Non-Virtuals Call Protected Non-Overloaded Virtuals Idiom ...
[23.3]
- Nondependent member-names (see also under Templates) ...
[35.19],
[35.20]
- Nondependent type-names (see also under Templates) ...
[35.18],
[35.20]
- Normal syntax: use when you can ...
[27.14]
- Not a dereferenced NULL pointer references ...
[8.7]
- Not one-size-fits-all (see also under Exceptions) ...
[17.5]
- Nuclear submarine ...
[21.2],
[21.3]
- NULL ...
[8.7],
[16.6],
[16.7]
- Number of copies made internally (see also under Exceptions) ...
[17.17]
- Numeric literal suffixes: L, U and f ...
[29.12]
- Numeric literals: naming them ...
[29.11]
- numeric_limits<T> ...
[15.3],
[15.6],
[35.8]
- Numerical Algorithms
- Numerical Recipes ...
[29.17],
[37.7]
|