>I would have different types:
>
> auto -- default. Behaves like variables in HyperTalk. Converts as
> needed. Slow.
>
> integer -- long int type in C
> real -- double type in C
Anthony,
I wouldn't want that. All variables should convert as needed, but only
*if* needed, e.g.:
on mouseUp
repeat with x = 1 to 100
get x & "th repeat"
end repeat
end mouseUp
would need to convert several times, but
on mouseUp
repeat with x = 1 to 100
beep x
end repeat
end mouseUp
should be optimized into an integer variable. Real data types should only
be required when using e.g. C libraries. Then, you should be able to
declare prototypes for C/C++ and Pascal routines as xTalk-like as possible,
but specifying the data types of parameters and return values so the types
are converted properly.
If we implemented exceptions, we could throw an exception on parameter
mismatch.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
