|
 | | P-brick Script code terminology
|
| Hi all, Perhaps someone can clarify this for me... I've been looking at the LEGO P-brick Script code language documentation that comes with the RIS 2.0 SDK PreAlpha. I was initially confused by the numerous references to program stacks. Does 'stack' (...) (25 years ago, 4-Apr-00, to lugnet.robotics.rcx)
| |
|  
event
(score: 0.944)
|
|
| |
|
event
(score: 0.943)
|
|
| |
|
event
(score: 0.943)
|
|
| |
|
event
(score: 0.943)
|
|
| | Re: Alternatives for NQC Event Support
|
| (...) I'm sorry its been taking so long. I was right in the middle of an overhaul to the NQC code generation classes when RCX 2.0 firmware was posted. This meant I had to finish the re-design before moving onto the simpler matter of an RCX 2.0 API. (...) (24 years ago, 4-May-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.943)
|
|
| |
|
event
(score: 0.943)
|
|
| | Re: Alternatives for NQC Event Support
|
| (...) I like the second option, find it more elegant and similar to analogous constructs in other languages. But I do see its possible side effects and misuses, so my final choice is option 3. Mario Web page: (URL) member page: (URL) member of (...) (24 years ago, 2-May-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.943)
|
|
| | Re: Alternatives for NQC Event Support
|
| (...) I can't wait. I've been holding off learning anything that might change... Does anyone know when RCXCC will support Scout downloading? Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 3-May-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.943)
|
|
| | NQC 2.x event processing
|
| Dave, I'm curious if the system of events and event-trapping in NQC 2.x will remain about the same as it is now. I played around with it this last week, and had little success (it worked once or twice, I *think*), but what struck me was how much I (...) (24 years ago, 4-Jun-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.942)
|
|
| | task switching strategy?
|
| I've been wandering through the kernal comparing it to similar kernals I have known or written, trying to understand the design choices. It appears that task are only switched at the 1ms timer interrupt and at yield() function call. yield() is only (...) (24 years ago, 21-Apr-00, to lugnet.robotics.rcx.legos)
| |
|
event
(score: 0.942)
|
|
| |
|
event
(score: 0.941)
|
|
| | Banging on the tasker
|
| (...) That's my plan. The nice thing about the tasker is that people can write code in a format they are more used to. The same things can be done with event driven single task code but it inverts the control flow. It is more meaningful for most (...) (24 years ago, 3-May-00, to lugnet.robotics.rcx.pbforth)
| |
|
event
(score: 0.941)
|
|
| | Re: NQC 2.x event processing
|
| (...) I don't have any changes in mind for the monitor/catch construct, although I'll listen to suggestions if people have any. There was a brief discussion about this a while back: (URL) that point I was already pushing a procedural approach - (...) (24 years ago, 4-Jun-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.940)
|
|
| | Re: NQC 2.2 a1 available for public test
|
| Working code using a counter. /* * lstop8.nqc - Line and Wall avoider * * Copyright (C) 2000 James Pritchard * * Date: 08-May 2000 * * * The contents of this file are subject to the Mozilla Public License * Version 1.0 (the "License"); you may not (...) (24 years ago, 8-May-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.940)
|
|
| | Re: NQC and rcx2
|
| (...) Documentation is always the last thing to get done.... Until I get it completed, your best bet is to read the lego documentation - especially the opcodes monel,monex,monal, and monax. The monitor/catch works like this: monitor(events) { // (...) (24 years ago, 25-May-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.940)
|
|
| | Re: NQC 2.x event processing
|
| (...) #3, which was the approach you took. (...) I think what I liked about the approach in pBrick script was that it was fairly like coding a microcontroller in assembler: set up an interrupt vector and then include a label and code for the (...) (24 years ago, 5-Jun-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.940)
|
|
| |
|
event
(score: 0.939)
|
|
| |
|
event
(score: 0.939)
|
|
| | Re: NQC 2.x event processing
|
| (...) Getting things like Timer[0] = 100; to work while still allowing if (Timer(0) < 100) { } is a lot harder than I had anticipated, so I'm punting on array-style setting of the various RCX source (such as Timer(), UpperLimit(), etc). There are (...) (24 years ago, 13-Jun-00, to lugnet.robotics.rcx.nqc)
| |
|
event
(score: 0.939)
|
|
| |
|
event
(score: 0.938)
|
