 | | Re: lsynthcp community development project setup on sourceforge
|
|
(...) I'd like to discuss changes before they are made, so I can keep track of new capabilities of the program. (...) Yes. I was trying to make lsynth not case sensitive when it came to recognizing keywords, but I don't like the fact that it changes (...) (21 years ago, 20-Jan-03, to lugnet.cad.dev)
|
| |
| | Re: lsynthcp community development project setup on sourceforge
|
|
(...) Yeah, I thought so. Other options are copying the line before the strupper(), or using strnicmp() or strncasecmp() for the keyword test. The copy method is easier to do in a portable way. (...) I like the named parameters. That makes it easy (...) (21 years ago, 20-Jan-03, to lugnet.cad.dev)
|
| |
| | Re: lsynthcp community development project setup on sourceforge
|
|
(...) What about getopt() style parameters, eg: -f foo.dat -l 20 -u cm --filename foo.dat --length 20 --units cm ROSCO (21 years ago, 20-Jan-03, to lugnet.cad.dev)
|
| |
| | Re: lsynthcp community development project setup on sourceforge
|
|
(...) Much better! I've been programming on Windows too much lately (isn't any amount too much? ;^) Kevin (...) (21 years ago, 20-Jan-03, to lugnet.cad.dev)
|
| |
| | Re: lsynthcp community development project setup on sourceforge
|
|
(...) Whoah, wait a minute! I like getopt() as much as anyone, but I thought we were talking about something to go *inside* the file on the SYNTH BEGIN line(s), not necessarily on the command line. Units may be universal for all synthesized parts in (...) (21 years ago, 21-Jan-03, to lugnet.cad.dev)
|
| |
| | Re: lsynthcp community development project setup on sourceforge
|
|
(...) ;^) Relax, we are talking about both on the command line that starts the program, as well as on the LDraw meta-commands that start synthesis of a specific part. Notice he said getopt() style parameters, not getopt() to get the parameters. (...) (21 years ago, 21-Jan-03, to lugnet.cad.dev)
|
