Subject:
|
Re: Getting rif off the 8.3 nomenclature???
|
Newsgroups:
|
lugnet.cad.dat.parts
|
Date:
|
Wed, 28 Mar 2007 22:58:14 GMT
|
Viewed:
|
5052 times
|
| |
|
|
In lugnet.cad.dat.parts, Kevin L. Clague wrote:
> In lugnet.cad.dat.parts, Travis Cobbs wrote:
> > In lugnet.cad.dat.parts, Kevin L. Clague wrote:
> > > I know that given the way LPub and LSynth are written and the language libraries
> > > used, switching away from the 8.3 limitation represents a significant amount of
> > > work.
> >
> > This suprises me. Can you elaborate on this? If we in the LSC are going to
> > make an informed decision on this issue, understanding why this is the case with
> > LPub/LSynth would help us greatly. I know all Win32 API calls work fine with
> > long filenames, and I had assumed that Delphi worked fine with them also. (LPub
> > is Delphi C++, right?)
> >
> > --Travis
>
> Travis it has to do with parsing. For type 1 lines and 8.3 I can simply use
> sscanf.
>
> Kevin
Sorry for posting to my own post. In particular if the "longer file names"
cannot have blanks in the names, then there is no problem for LPub or LSynth.
20.3 would require no changes at to LPub or LSynth.
Given that sscanf splits things up by whitespace, I think LPub and LSynth would
misparse file names with blanks or tabs in them.
As I said, Willy has a good argument, and well worthy of consideration.
I think that as long as there is embedded white space is not allowed, the change
will be backward compatible and not cause problems (at least not for LPub and
LSynth).
The only issue is that this is a pre/co requisite situation. We'd want to make
sure we know what programs will have problems, and which ones don't. If there
are none, then there is no issue.
I think those authors that want their programs to be continued to be used (like
myself) will make any changes neccessary, but those programs that are no longer
supported *might* not work in the future.
Kevin
|
|
Message has 3 Replies:
 | | Re: Getting rif off the 8.3 nomenclature???
|
| (...) OK, that makes a lot more sense. LDView had the same problem with whitespace in filenames until I specifically added support for that. (LDView now gives you a warning when it encounters whitespace in a filename.) --Travis (18 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
| | | Re: Getting rif off the 8.3 nomenclature???
|
| (...) I very strongly support allowing the inclusion of whitespace in LDraw filenames, provided the first character is not whitespace. Bricksmith has always allowed users to do this. When parsing a line, I get all the matrix numbers, skip all (...) (18 years ago, 2-Apr-07, to lugnet.cad.dat.parts, FTX)
|
Message is in Reply To:
25 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
