<<Brian,
I think that, recalling past problems with 32k limits in HyperCard, we
might be best off with allowing very long names for buttons and fields...>>
Heh heh, yes I see your point =). Assuming it doesn't become a headache, I
vote for variable length strings. Perhaps NULL-terminated, if that is to be
the native string type anyway? Or else a p-string with two length bytes? I
really can't imagine anyone wanting object names longer than 65536 characters
=P...
BTW, while we are on the 32k note, are we planning to build this on top of
WASTE instead of TextEdit? Does WASTE have a Windoze port (lest we have to
use two engines to be cross-platform)?
I'll be looking forward to the next snapshot- I'll have to break out my
Hypercard Script Language Guide and find some commands to crank out (and
crank up hopefully).
Brian
