> I suspect that "path" abstraction was created a means for manipulating file
> pathnames in a way that is cross-platform and also less prone to error than
> using strings.
That's the impression I get from this section in the reference:
http://docs.racket-lang.org/reference/pathutils.html
Th
Don Green wrote at 05/12/2012 12:44 PM:
Maybe I need to understand why Racket is using the path form instead
of the string form. (Can you explain briefly why the string data type
was not sufficient so the path data type was developed.
I suspect that "path" abstraction was created a means for m
What are some guidelines about use of paths?
Am I correct in thinking the following is a path:
#
Should I specify paths, such as above, rather than strings such as:
"/home/don/.plt-scheme/4.2.1/collects/DG/append2.ss"
(I notice that many Racket path functions convert my strings to paths. I
want t
3 matches
Mail list logo
