Re: [vos-d] datatypes
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 positions in 3d space. http://www.epsitec.ch/colobot/program/prog050.txt ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] datatypes
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 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? -- [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ] signature.asc Description: Digital signature ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] datatypes : How is 'point' different?
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 [EMAIL PROTECTED] wrote: 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 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? ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
Re: [vos-d] datatypes
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 recently occurred to me that some important languages don't have unsigned types (Java being the main one, but also many dynamically typed languages only have a single integer or number type). Does it make sense to axe unsigned types from the basic core types in the interests of harmony between languages, or do we want as diverse a set of basic types as possible and leave it up to the language binding to deal with it? (Then you have to figure out what the correct behavior is when you pass in a negative number to an unsigned type...) Python doesn't have unsigned types, but the functions that convert data between C and Python know about them. I'm not quite partial either way; I like unsigned for blobs, as you say. Although arguably blobs should be strings... best, Lalo Martins -- So many of our dreams at first seem impossible, then they seem improbable, and then, when we summon the will, they soon become inevitable. -- personal: http://www.laranja.org/ technical:http://lalo.revisioncontrol.net/ GNU: never give up freedom http://www.gnu.org/ ___ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
