🚀 go-pugleaf

>>>>> "TP" == Tom Payne <thp@cs.ucr.edu> writes:
[...]
TP> This is probably the hub of our difference: I have difficulty
TP> imagining a reasonable architecture that does something other than
TP> ignoring or trapping the reading of invalid pointers.  (Granted,
TP> "reasonable" is in the eye of the beholder.)

On the contrary, I think it could be a quite common thing. Many
architectures memory-map I/O and it's perfectly imaginible that:

	int x = *p;

where p is an invalid pointer triggers some I/O operation because
p happens to point into such an ``I/O area''. The standard cannot
reasonably be expected to say what can or cannot happen in those
cirucmstances.

	Daveed
---
[ comp.std.c++ is moderated.  To submit articles: Try just posting with your 
                newsreader.  If that fails, use mailto:std-c++@ncar.ucar.edu
  comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html
  Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html
  Comments? mailto:std-c++-request@ncar.ucar.edu 
]