 | | Re: PRGM button - am I missing something? —Ben Jackson
|
| | | (...) I think you need `dll -p0 foo.lx' and `dll -p1 bar.lx'. That syntax is working fine for me. Right now my battery meter is in slot 0 (fading fast!) and the program I'm debugging is in slot 1. --Ben (25 years ago, 12-Jan-00, to lugnet.robotics.rcx.legos)
|
| | | |
| | | | | Re: PRGM button - am I missing something? —Markus L. Noga
|
| | | | Ben Jackson schrieb: (...) If getopt is working right, the position of switches shouldn't matter. If they do, it's broken. Markus. (25 years ago, 12-Jan-00, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: PRGM button - am I missing something? —Ben Jackson
|
| | | | (...) From getopt(3) on BSD and other systems: When all options have been processed (i.e., up to the first non-option argument), getopt() returns -1. However, from the Linux manpage: By default, getopt() permutes the contents of argv as it scans, so (...) (25 years ago, 12-Jan-00, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: PRGM button - am I missing something? —Markus L. Noga
|
| | | | Ben Jackson schrieb: (...) OK, I'll change the docs and examples, then. Too bad, I thought position-independence very nifty indeed. Markus. (25 years ago, 12-Jan-00, to lugnet.robotics.rcx.legos)
|
| | | | |
| | | | | | Re: PRGM button - am I missing something? —Jeff Chrisope
|
| | | | (...) Yep, the option order was the problem on Windows. getopt does indeed happily ignores any options found after the first non-option. Thanks again! -Jeff p.s. And don't worry, I can take any Windows jabs you have to offer - I've heard 'em all. (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.legos)
|
| | | | |
