 | | 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)
|
