the use of id's vs. handles
Posted: Sun Apr 11, 2004 2:39 pm
reading through the remarks on the new upcoming version of pb, including the beta, i couldn't help but let my mind wander and started fearing code breaks...
although in concept i applaud the use of pointers and the removal of the mem id parameter, i worry about the incompatibility with all old samples and code
why not simply change the syntax to
allocatememory(-1, ....)
and modify freememory to accept either the windows handle or the pb memory id?
just a personal opinion
come to think of it, why not use a different general approach:
low numbers are id's
high numbers are windows handles
that would remove the need for the many windowid() calls etc.
in other words:
allocatememory( n , ....) old style
allocatememroy( -1 , ....) new style
freememory ( n ) old style
freememory (n ) with n a high number new style
same for the windowid() stuff
why use windowid() in a command, when the value could be passed of the handle directly? i assume here the handle will be also in the range 4mb or higher, thus providing a clear distinction between old style and new style
i know sometimes code breaks are part of the improvement of a language, but wouldn't the above be a better way? anyway, it's fred's decision, it won't alianate me, but it might alienate newcomers that try samples from the archives
although in concept i applaud the use of pointers and the removal of the mem id parameter, i worry about the incompatibility with all old samples and code
why not simply change the syntax to
allocatememory(-1, ....)
and modify freememory to accept either the windows handle or the pb memory id?
just a personal opinion
come to think of it, why not use a different general approach:
low numbers are id's
high numbers are windows handles
that would remove the need for the many windowid() calls etc.
in other words:
allocatememory( n , ....) old style
allocatememroy( -1 , ....) new style
freememory ( n ) old style
freememory (n ) with n a high number new style
same for the windowid() stuff
why use windowid() in a command, when the value could be passed of the handle directly? i assume here the handle will be also in the range 4mb or higher, thus providing a clear distinction between old style and new style
i know sometimes code breaks are part of the improvement of a language, but wouldn't the above be a better way? anyway, it's fred's decision, it won't alianate me, but it might alienate newcomers that try samples from the archives