This is where OPTIONAL 'typing' would be very, very useful.
sqb
http://support.runrev.com/bugdatabase/show_bug.cgi?id=2813
------- Additional Comments From [EMAIL PROTECTED] 2005-07-04 17:28 -------
After giving this much thought, I don't believe that it is needed to have a
seperate array subprocessor. Transcript could provide the speed needed for
processing arrays in a simpler way. If Transcript had an array
declaration command
that allowed the user to fix the dimensions and data size/type for
an array and
limited the "keys" to integer indexes, then high speed array
processing could be
built-in. The key is that once an array is fixed in size and type, the
compiler/runtime does not need to do extensive checking of the data
to determine
the operation code. The compiler can then generate the code for a
much simpler
runtime operator. These declared arrays would run 10 to 100 times
faster than the
typless ones for the kind of operations that are required by image
processing, AI,
statistics, and many other applications.
----------
Posted by RevZilla 2.0.3
------- You are receiving this mail because: -------
You are a voter for the bug, or are watching someone who is.
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
