[vos-d] datatypes : How is 'point' different?

[S Mattison]

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 1/24/07, Peter Amstutz <tetron at interreality.org> wrote:
>
>
>
> On Wed, Jan 24, 2007 at 11:22:48AM -0700, S Mattison wrote:
> > On 1/22/07, Peter Amstutz <tetron at interreality.org> 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 possible, in favor of
> breaking out data into separate, meaningful fields whenever it makes
> sense.  That said, stream-encoded data (particularly compressed formats)
> does often need to be treated as an opaque blob.  However, in the
> context of the original discussion the current design has a "uint8"
> type, so the function of blobs is filled by using an array of unsigned
> bytes.  Only if we don't have unsigned integers is a "blob" type needed.
> Although in that case you *still* need to figure out an appropriate
> mapping of your blob type into the target language.
>
> > Have you looked at the 'game' called Colobot? Their "3d bot
> > programming language" has a data-structure called "Point", for
> > positions in 3d space.
> > http://www.epsitec.ch/colobot/program/prog050.txt
>
> Um.  How is a "point" different from a normal x,y,z vector?