[Ldlite-development] Re: Too much ldlite compatibility.

[Paul G. <pg...@ya...>]

Hey, good progress.  You know, I've set out on
a bug hunt more than once to nail that no-CR 
problem.  There is a performance hit of more than
50% in the lex/yacc to handle the problem, but
I think I messed it up when I changed to having
the top level be a string in memory rather than
an actual file.  I'll pencil in some time over
Thanksgiving break to fix it, if not sooner.

The asociation with .dat is done automagically
by windows/MFC.  I'll find a way to disable it,
or at least ask first.

BTW, are you on the ldlite-development mailing
list at sourceforge? Archiving this stuff makes
it easier to look up later, so we should use
the list instead of private email.
-gyug


--- Don Heyse <don...@us...> wrote:
> Hi Paul,
> 
> I'm almost done merging the ldlite and ldglite
> source code.  I've gotten to
> the point where the ldglite parser behaves just like
> the ldlite 2.3 parser.
> Too much in fact.  The way it silently drops type 1
> lines if there is no
> CR at the end of the file is driving me nuts.  I
> can't really follow the 
> parsing code but I may have some info that could
> help.  I created two dat
> files that include studline.dat and put a CR at the
> end of one, but not the
> other.  When I enabled the debugging in the parser
> and diffed the results
> I saw that they diverged at a tEOF symbol vs a tEOL
> symbol.  See the pic in
> http:\\ldglite.sourceforge.net\ldliteEOF.zip 
> 
> So I started comparing the 1.6 source and the 2.3
> source of ldlite.y and
> discovered lines 863 to 875 of ldlite.y.  You seem
> to have left out this
> chunk of code from the tEOL version of ObjectLine
> around line 904.  Could
> this
> be the cause of the problem?
> 
> I decided not to change the way
> ldraw_commandline_opts.F is used in stub.c 
> after all.  It turns out that I needed more of a
> display mode stack so I
> left
> ldraw_commandline_opts.F as the top of the stack in
> my code. 
> 
> Hey, and if you manage to roll a new release soon,
> could you disable the 
> "feature" that takes over the .dat file extension
> every time you run ldlite?
> That also drives me nuts.  Whenever I compare things
> results with ldlite 2.3
> I have to reset my mime types back to use ldglite. 
> I don't think ldlite 1.6
> worked this way.
> 
> Have fun,
> 
> Don
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com