| |
In lugnet.cad.dev, Steve Bliss writes:
> In lugnet.cad.dev, Lars C. Hassing writes:
>
> > It's OK with me to use e.g. "0 IFDEF L3PPOV"
>
> OK. I'll write up a spec/reference page on 0 IFDEF. It will include the
> following metacommands:
>
> 0 IFDEF <code>
> 0 IFNDEF <code>
> 0 ELSE
> 0 ENDIF
>
> Should there be a 0 ELSEIFDEF and/or 0 ELSEIFNDEF?
>
> > The POV code is (or can be) L3P related.
> > As an example of that see e.g. Chuck Sommerville's minifig head
> > http://www.brickshelf.com/gallery/chucks/Dats/3626bp04.dat
>
> Hmm. That's not particularly keen. IMO. Not that I can see any way
> around it.
Which part of it aren't you keen about? Is it all the extra stuff in
the dat file? If so, then perhaps this is a good time to dredge up
my 0 INCLUDE suggestion yet again. ;)
http://news.lugnet.com/cad/dev/?n=6636
Don
|
|
Message has 1 Reply:
 | | Re: Inline POV-Ray code?
|
| (...) No, I meant the POVRay code referring to L3P-generated objects. By allowing this code in official part files, we'd be endorsing language that hasn't been generally discussed and reviewed. Not that I see any particular problem with the code. (...) (25 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
Message is in Reply To:
| | Re: Inline POV-Ray code?
|
| (...) OK. I'll write up a spec/reference page on 0 IFDEF. It will include the following metacommands: 0 IFDEF <code> 0 IFNDEF <code> 0 ELSE 0 ENDIF Should there be a 0 ELSEIFDEF and/or 0 ELSEIFNDEF? (...) Steve (25 years ago, 27-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
26 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
|
|
|
|
