Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #84399
| From | ram@zedat.fu-berlin.de (Stefan Ram) |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | "std::" (was: Wikipedia) |
| Date | 2022-05-31 19:34 +0000 |
| Organization | Stefan Ram |
| Message-ID | <std-20220531203211@ram.dialup.fu-berlin.de> (permalink) |
| References | (7 earlier) <t75n2t$e0r$1@gioia.aioe.org> <20220531193724.00002611@reddwarf.jmc.corp> <t75nig$kog$1@gioia.aioe.org> <20220531200041.00002b0e@reddwarf.jmc.corp> <t75poc$1mbm$1@gioia.aioe.org> |
muttley@dastardlyhq.com writes: >Right, because having the visual noise of std:: all over the sodding place >really makes for clear code. Does this refer to "::std" or some local namespace "std"? So, I hope you see: We need to always write "::std::"! Well, in theory I could imagine an editor that shows you "::std::cout" as "cout" in blue, but writes out "::std::cout" when you save it to a file. But in practice no one could write such a complicated editor. When typing, you would type "::std::cout ", and then it would be converted to a blue "cout ", or you could have some hotkey that toggles blueness when the cursor is in it.
Back to comp.lang.c++ | Previous | Next | Find similar | Unroll thread
csiph-web