 | | RE: Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) Well what about an indexation based on a sensor value? How could your compiler know the range the sensor has? Sample: int volatile *color_sensor = (int *) 0x4000; int getColor(void) { static int color[4] = { 123, 456, 789, 111 }; return (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | RE: Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) Well what about an indexation based on a sensor value? How could your compiler know the range the sensor has? Sample: int volatile *color_sensor = (int *) 0x4000; int getColor(void) { static int color[4] = { 123, 456, 789, 111 }; return (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Re: How many people signed up for the NXT Developer's Program?
|
|
(...) I'm a software engineer, and I've written and tested code in many fields- education, games, graphics hardware, and web sites. All of these give me insight that should help me thoroughly test the suitability and functionality of both the (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) Why? Full Java requires it but you're not trying to make a full Java implementation. Why can't all your data be statically allocated by the compiler (not allocated at run-time)? Sure, you'd have to tweak the language a little but so what? (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) I was looking into Java as a small-robot programming language and examined a few implementations. I came to the conclusion that it simply wasn't suitable. Sure you can shoehorn a cut-down version into a small processor but you've had to (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
