Subject:
|
Re: Getting rif off the 8.3 nomenclature???
|
Newsgroups:
|
lugnet.cad.dat.parts
|
Date:
|
Wed, 28 Mar 2007 22:35:17 GMT
|
Viewed:
|
4636 times
|
| |
|
|
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
|
|
Message has 1 Reply:
 | | Re: Getting rif off the 8.3 nomenclature???
|
| (...) 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 (...) (17 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
Message is in Reply To:
| | Re: Getting rif off the 8.3 nomenclature???
|
| (...) 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 (...) (17 years ago, 28-Mar-07, to lugnet.cad.dat.parts)
|
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
|
|
|
|
