On 1/22/07, Peter Amstutz [EMAIL PROTECTED] wrote:
Alternately we could also have a blob type for this case.
I'm a big fan of the Blob type. I do a lot of SQL database work. ;)
Have you looked at the 'game' called Colobot? Their 3d bot
programming language has a data-structure called Point, for
On Wed, Jan 24, 2007 at 11:22:48AM -0700, S Mattison wrote:
On 1/22/07, Peter Amstutz [EMAIL PROTECTED] wrote:
Alternately we could also have a blob type for this case.
I'm a big fan of the Blob type. I do a lot of SQL database work. ;)
Well, the goal is to avoid blobs as much as
Other than; all you have to type is 'point' to declare it, and it maps
cleanly to 'position' methods and properties, whether you're defining
point.x = item.position.x or point = item.position?
Err... Probably not too far different.
It's just a neat way to orient your 3d objects, imo.
-SM
On
On Mon, 22 Jan 2007 10:07:43 -0500, Peter Amstutz wrote:
Quick technical design question I wanted to throw out for debate:
unsigned types. The current s5 design calls for 8, 16, 32 and 64 bit
signed and unsigned integer types, in addition to single- and
double-precision floats. It
