Is there a reason for the absence of a `current-directory` primitive?
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.
If not, can it be added?
My initial inclination is that this sort of thing is fringe enough that,
if you wanted it, it would be best provided by an extension. I could be
convinced that I'm wrong.
Is there an practical use case that you have in mind for this primitive?
On 03/02/2015 03:54 PM, Alan Isaac wrote:
Is there a reason for the absence of a `current-directory` primitive?
If not, can it be added?
Today I was walking students through some basic file manipulation at
the command line, and one asked me how to determine his current
directory. The best suggestion I could come up with was to set it
explicitly with `set-current-directory`. (I did not want to discuss
the `shell` extension.)
Thanks,
Alan Isaac
--
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.
