Subject:
|
Re: NXT Optimized Array Handling
|
Newsgroups:
|
lugnet.robotics.nxt
|
Date:
|
Sat, 6 Jan 2007 14:48:50 GMT
|
Viewed:
|
12128 times
|
| |
|
|
Thanks Dick,
I also found info on how arrays are handled in the Executable File Spec. I
didn't see it before. My cut on this is that I will use single-dimension
arrays in non-time-critical areas and avoid mult-dimensional arrays
alltogether. It sounds like there is a lot of copying and memory
alloc/freeing going on that could be very inefficient. This seems to be in
support of their polymorphism of byte codes. Maybe I'll do an analysis
someday when I'm bored :-).
David
"Dick Swan" <dickswan@sbcglobal.net> wrote in message
news:012001c72c22$ca4de040$0e0ba8c0@dickdesktop...
>
> I would suggest that the easiest way to understand how standard firmware
> handles arrays is to go to the NI web site and do a search on something
> like "efficient LabVIEW memory management" which will result in a nice
> description of how LabVIEW handles arrays. And then assume that the
> NXT-G firmware does something quite similar.
...
|
|
Message is in Reply To:
 | | RE: NXT Optimized Array Handling
|
| I would suggest that the easiest way to understand how standard firmware handles arrays is to go to the NI web site and do a search on something like "efficient LabVIEW memory management" which will result in a nice description of how LabVIEW (...) (18 years ago, 30-Dec-06, to lugnet.robotics.nxt)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in NXT programmable brick
|
|
|
|
|
|
