Darren New wrote:
Christopher Smith wrote:
Darren New wrote:
... added to the fact that many current languages make such
side-effects
difficult to determine.
Well, it depends on how you define "current languages" and "difficult to
determine".
No, it depends on noticing the word "many" in there. ;-)
I'm talking about C aliased pointers, interrupts/signals happening in
the middle, etc. Natually, things like purely functional languages,
or imperative languages with built-in high-level looping constructs
(like SQL) can make it much easier for the compiler.
So basically you are talking about a problem with C, and in fact a
problem that is at least partly address by C99's standardization of the
"strict" keyword. Which for me at least requires a curious definition of
"current languages".
For an idea of how even C++ can get around these problems, take a look
at Blitz++.
--Chris
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
