At 10:36 PM 11/3/2001 -0800, Brent Dax wrote:
Well, for now we're using Perl for Configure, but that won't be possible
in the final version. Nasty bootsrapping issues with that. :^)
You'd be surprised... :)
Seriously, miniparrot, enough to do simple file ops, spawn external
programs and
Dan Sugalski:
# At 10:36 PM 11/3/2001 -0800, Brent Dax wrote:
# Well, for now we're using Perl for Configure, but that won't
# be possible
# in the final version. Nasty bootsrapping issues with that. :^)
#
# You'd be surprised... :)
#
# Seriously, miniparrot, enough to do simple file ops, spawn
At 11:12 AM 11/4/2001 -0800, Brent Dax wrote:
Dan Sugalski:
# At 10:36 PM 11/3/2001 -0800, Brent Dax wrote:
# Well, for now we're using Perl for Configure, but that won't
# be possible
# in the final version. Nasty bootsrapping issues with that. :^)
#
# You'd be surprised... :)
#
# Seriously,
On Sat, 3 Nov 2001, Zach Lipton wrote:
parrot. The idea is to have the Configure.pl script itself run .cm files
located in Config/, these .cm files (configuremodule) would do the actual
work of configuration. The Conf.pm module would contain a set of API's for
the .cm files to call. (this is
Zach Lipton:
# Ok, great. Thanks. I'll see what I can do.
#
# Random idea off the top of my head, note that this assumes
# that configure
# will use perl to work, if this is not going to be true, this
# probably won't
# work.
Well, for now we're using Perl for Configure, but that won't be
