Re: static virtual is a keyhole?
"White Wolf" <[email protected]> Sun, 12 Oct 2003 08:26:40 +0300
| Newsgroups | gmane.comp.programming.keyholes |
|---|---|
| Message-ID | <01e401c39081$6a9e3540$568dba50@Evo> |
Scott Meyers wrote: > const volatile int z = 10; // may z be placed in ROM? may it be > // changed? may z be placed in ROM? - Nope. may it be changed? - Not by the language I have actually seen a program using such a variable. It was for a read only register of a HW device. You could read it, but not write to it (hence the const). OTOH the HW itself was changing this value all the time, so it had to be volatile. It does make sense. But it was looooong time ago when I have seen this. DOS world, not even 6.2. > We already have plenty of terms that are so broad, nobody knows what > they mean. (E.g., "object-oriented," "pattern.") My preference is > to try to keep that from happening to "keyhole." So I cannot call tourist class seats of long-haul flights a keyhole then. I have to stick with sardine-can. :-) White Wolf