 | | Re: Another RcxCC revision
|
|
hi John, Fantastic that you released your sources !! That's a good reason for me to try and test your program. I haven't found the time to do it. Also I'll try to compile your sources and look into them. I'll let you know my experiences. (...) met (...) (23 years ago, 12-May-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Another RcxCC revision
|
|
I just uploaded another revised rcxcc.zip file to my website. (URL) isn't changed significantly from the version I uploaded last night. I cleaned up the source code and removed obsolete references to units that aren't used now that I've abandoned (...) (23 years ago, 12-May-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: API changes
|
|
I'm actually on my way to my baccalaureate ceremony right now, but I do want to say that I feel very strongly that API changes for the sake of API changes should not be checked in. The current API, while not always intuitive, is well documented and (...) (23 years ago, 12-May-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC's RCX Communication Code
|
|
(...) You'll need a bunch of files from the rcxlib directory (primarily RCX_Link.cpp, which implements the communication protocol). You'll also need the serial interface code which resides in platform/PSerial_unix.cpp (plus a few include files in (...) (23 years ago, 12-May-01, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: API changes
|
|
(...) I don't imagine that these changes will increase memory usage much, since they are largely just re-working existing features. I will look into the memory usage before releasing, though. In fact, I think that after I redid the networking a bit (...) (23 years ago, 12-May-01, to lugnet.robotics.rcx.legos)
|
