 | | Re: Calling all Meta-commands
|
|
(...) I agree. (...) Nit: we've already *got* an LDraw file format spec. Next item! (...) 'Control' is heavy-handed for my tastes. 'Support', 'endorse', 'coordinate' are all better. All a standards body could do is manage the documentation, and (...) (22 years ago, 21-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Dan, You program in *Perl*. Of course you think it's good to always have punctuation. You probably think more punctuation == better. ;) Steve (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) True, but that's no reason to have (unnecessary) complications. The computer will understand whatever we set it up to understand. LIGHTVALS, {LIGHTVALS}, 32.6, it's all the same to the silicon. Syntax is for users, beginning or advanced. If we (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Depends on how open or closed the SB is. I think there's a place for part authors and users as well as developers. Steve (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) Tim, I've been reading this thread, and you keep mentioning this 'Steve' person. 'Steve this' and 'Steve that'. I must have gone through 100 messages by now, and no 'Steve' has shown up. I'm beginning to suspect you are imagining this 'Steve' (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Backwards Compatibility (Was Calling all Meta-commands)
|
|
(...) I really agree with Dan on this point. As I mentioned in another message, a standards body could certainly come up with suggestions for standard commands, but they wouldn't have any power of enforcement. About the only thing ldraw.org could[1] (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Because it wouldn't be supported by LDraw and LEdit. Part files frequently include comments, so any standard option for commenting should be allowable in the parts library. (...) Some people already use COMMENT. Steve (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) Rosco, Unfortunately, MLCAD's use of WRITE is a really bad example, because MLCAD is mis-using an already standard meta-command. Plus, 0 WRITE statements are not allowed in official parts, so any part authors who create their files in MLCAD (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) I support that (general) guideline. The only real difficulty is if the meta-command becomes generally accepted, and is 'promoted' to being an accepted standard. We'd either want a different prefix for org standards, or no prefix. Either way (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
| |
| | Re: Calling all Meta-commands
|
|
(...) I agree with Larry -- support it publically. Recognize '0 LTrax xxxx' as the primary syntax for the command. Especially, let the author of the original command know that you are implement their command. Hopefully, that will give them cause to (...) (22 years ago, 22-Mar-03, to lugnet.cad.dev)
|
