Andy Dougherty:
# On Wed, 19 Sep 2001, Brent Dax wrote:
#
# > Andy Dougherty:
# > ...
# > # +prompt("And what is sizeof(iv)?", 'ivsize');
# > # prompt("And your floats?", 'nv');
# > # +prompt("And what is sizeof(nv)?", 'nvsize');
# > ...
# >
# > Somehow, this seems like something we ought to be able to do
# > programmatically. Can't we just compile a quick little C
# program with
# > something like:
# >
# > printf("%d/%d", sizeof(${iv}), sizeof(${nv}));
# >
# > in it, and then parse the output? I don't like asking
# users stuff like
# > their int sizes--too prone to confusion and mistyping.
#
# Oh, sure, though I wouldn't worry too much about current
# Parrot "users"
# being unable to handle such things -- for the most part it'll
Hey, even the best programmer can accidentally hit 7 instead of 4 (see
your numeric pad). We should ask as little as possible (without losing
flexibility), and infer everything else.
# pick them up
# correctly from the Configure defaults from the perl5 being
# used to build
# Parrot. (If run as part of an automated smoke test, for
# example, we'll
# possibly pick up all sorts of 32/64 permutations.)
#
# However, you're right. The Configure mechanism ought to be able to
# compile and run a small program. The interface for doing
# that ought to be
# set up before too much effort is made splicing it in ad-hoc. Having
# someone else do that hard work has been one of my main goals :-).
I'll work on it later today.
--Brent Dax
[EMAIL PROTECTED]
They *will* pay for what they've done.
