I would say that there is indeed a compelling reason to know what the
working directory is when one starts writing to files!
In that case, rather than just dumping files where ever NetLogo happens
to think the current directory is, it seems more sensible to me to
explicitly state where you want your file to go, which is already
something well within your power in NetLogo.
On 03/03/2015 11:34 AM, Alan Isaac wrote:
On Tuesday, March 3, 2015 at 12:13:15 PM UTC-5, Jason Bertsche wrote:
I guess I would turn the question around here and ask if there's a
compelling reason for the presence of such a primitive. It's not
obvious to me what good it would really do to know where a model
was launched from and why the model's behavior should change based
on that.
In the situation I described above, no model was launched. I had the
students launch NetLogo in order to experiment at the command line. I
would say that there is indeed a compelling reason to know what the
working directory is when one starts writing to files!
In response to Nicolas, as I said, I did not want to have to introduce
extensions in the middle of this discussion, and certainly not
extensions that are not bundled! You may have forgotten what it's
like, but introducing students to file-based IO is already a complex
undertaking. (Many of my students have never seen a programming
language before.)
In response to Frank, it is an interesting proposal. The difference
between e.g. `file:open` and `file-open` seems nothing to sweat
about. It would certainly be nice to have a fuller and more
traditional file-system support.
--
You received this message because you are subscribed to the Google
Groups "netlogo-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"netlogo-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
