 | | Announcing BricxCC release 3.3.5.6
|
|
(...) I was updating the website earlier today which may have caused some disruption. The link worked for me a few minutes ago. This is as good a time as any to post about my new release of BricxCC. Version 3.3.5.6 fixes an Access Violation during (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc, lugnet.robotics.scout)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
(...) Thanks for conducting the test... being 200+ miles away from my RCX this was bugging me :). My sources (gcc-2.95.2) have the same #define... but with the following about 120 lines earlier: /* Make int's 32 bits. */ #define TARGET_INT32 (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Gutting an optical mouse - Part I
|
|
(...) Gee, that's too bad. That means there are only three states that can be distinguished. It seems like they could have easily increased the resolution by 1/3, without any cost. (23 years ago, 12-Jul-02, to lugnet.robotics)
|
| |
| | Re: anyone know how to check free space on RCX?
|
|
John A. Tamplin, Jason Clark, Jochen Hoenicke and Michael J Ash: Thank you all for addressing these issues! It all make sense after reading the preceeding messages. I appologize for causing confusion. I am glad, however, to get it straight. ??So (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | detecting memory leaks
|
|
In the thread "anyone know how to check free space on RCX?" the issue of checking for memory leaks was raised. I wanted to mention that I have some code that may help in that area. I wrote a function for the memory manager called mm_defrag() It (...) (23 years ago, 12-Jul-02, to lugnet.robotics.rcx.legos)
|
