Subject:
|
Re: LDGLite bug report (yes, one more)
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Tue, 14 Aug 2001 13:56:47 GMT
|
Viewed:
|
514 times
|
| |
|
|
In lugnet.cad.dev, Jacob Sparre Andersen writes:
> Don:
> > This could be the ldlite large MPD bug again.
> > You could try increasing it some more and recompiling. Look for
> > this in lex.yy.c
> >
> > #define MAX_CACHED_TOKENS (10*1024)
> > #define MAX_MPD_CACHED_TOKENS (16*1024)
> > #define MAX_CACHED_FILES (24*128)
> >
> > Replace the 10, 16, and 14 with bigger numbers and try it.
>
> I'll try this.
You should at least try the "-l3" before you recompile. I'm sort of
interested in what you get for render times with both parsers. I only
have somewhat underpowered PCs to work with, so I'm curious how they
compare in the "real world".
Don
|
|
Message has 2 Replies:
 | | Re: LDGLite bug report (yes, one more)
|
| Don: (...) Okay. Doing that now. The errors in the ortographic projection rendering seem to be independent of the parser. You can see an image at: (URL) corresponding command line is: ldglite -ms -i1 -s0.2 -j -l3 ~/Projekter/LEGO/Dat...D/town.mpd (...) (23 years ago, 14-Aug-01, to lugnet.cad.dev)
| | | Re: LDGLite bug report (yes, one more)
|
| Don: (...) Using the "l3" parser: $ time ldglite -ms -i1 -s0.2 -l3 town.mpd ... 281.790u 21.700s 8:48.81 57.3% 0+0k 0+0io 2290pf+0w $ A total of 303.49 seconds. The result: (URL) the "ld" parser: $ time ldglite -ms -i1 -s0.2 -ld town.mpd ... (...) (23 years ago, 14-Aug-01, to lugnet.cad.dev)
|
Message is in Reply To:
21 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
|
|
|
|
