The read only attribute on mapped files is something I use all the
time because of a behavior that is intertwined (I think) with this
discussion. I have been burned by the fact that if a file is mapped
with name RO and then a verb is called, say
oops RO
oops =: 3 : 'y =. scramble y'
then your mapped file is "scrambled" - this behavior seems very
contrary to the spirit of j, but I lost all arguments about it.
Happily I can try to be very vigilant to map my critical (not to be
changed during "analysis") database files as read only. I try to be
very careful to do just that, but ....
- joey
At 11:41 -0500 2008/11/20, Raul Miller wrote:
On Thu, Nov 20, 2008 at 10:00 AM, Mark D. Niemiec
<[EMAIL PROTECTED]> wrote:
Unfortunately, this can't be used to create read-only verbs or oprators,
at least not transparently. I'm not sure exactly how you're doing the
read-only magic specifically, but ...
A search against site:jsoftware.com shows that the "read only data"
error message has to do with the use of mapped files.
This implies that this mechanism is limited to the kinds of things that
can be represented using mapped files.
--
Raul
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
