| |
In lugnet.cad.dev, Tore Eriksson wrote:
> But if you call the procedure SaveToFile(Path+FileName) to save on the disk,
> then the path has to be valid.
Right. Any "MPD splitter" program should include code to check that
filenames and paths are valid, and either report missing paths, or
create them, or ask the user before creating them, or provide options
(ie, command line parameters) to control how the program should deal
with embedded paths.
> (As an experiment, I named a subfile of an MPD file *++0GGG\\\:::00.dutt and
> L3Lab had no problems with that. As long as you don't have to write it to
> disk, anything seems ok.)
:)
I tried '0 FILE ?'. It worked just fine.
Steve
|
|
Message is in Reply To:
 | | Re: MPD spec
|
| (...) I don't know how ldglite and other parsers work, but I guess they don't create files with paths and all, but rather objects somewhere in RAM, with 'filenames' just as a property. But if you call the procedure SaveToFile(Path+FileName) to save (...) (23 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
65 Messages in This Thread:
 
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
