 | | Re: useful battery program
|
|
Ben Jackson schrieb: (...) Saved my life a couple of times, when LNP was locking up the system in an entirely incomprehensible way. (I'd really appreciate "Unreachable code" warnings sometimes... or maybe they scrolled away.) (...) How about this: a (...) (25 years ago, 12-Jan-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: PRGM button - am I missing something?
|
|
(...) 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?
|
|
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?
|
|
(...) 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?
|
|
Hi Jeff, Jeff Chrisope schrieb: (...) There could be a problem with getopt in the Windows-libc. Try inserting a printf after the loop dealing with options, to show which program slot dll is actually transmitting to. (...) Hey, aren't you with (...) (25 years ago, 12-Jan-00, to lugnet.robotics.rcx.legos)
|
