On 4/23/07, Dan Bron <[EMAIL PROTECTED]> wrote:
In the example I gave, the memory was already allocated. I simply modified it.
Another exploit: I could map a read-only file in one process, and map
that into J as a share. Good luck applying your eradicator to that.
The bit pattern which we currently associate with
"negative zero" would remain as a potential bit pattern.
However, if execution time is not an issue, I do not see why J should
have to treat this as a valid bit pattern in the context of floating
point numbers.
--
Raul
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
