Simon Cozens:
# Yeah, that was it! Brent, do you want to take care of that.
# (config_h.in would be better, since it gets mindshare from the
# current Perl 5 build process.)
Didn't take long--patch below sig. You'll also have to rename
config.h.in to config_h.in yourself.
--Brent Dax
[EMAIL PRO
4, 2001 01:41
# To: [EMAIL PROTECTED]
# Subject: Re: Things we need to do.
#
#
# On Thu, Sep 13, 2001 at 09:48:27PM -0400, Dan Sugalski wrote:
# > Ah, I'm sure it was a slip 'o the keyboard. :) config.h_in
# (or config_h.in)
# > are both OK, and unique enough on 8.3 systems.
#
# Yeah,
On Thu, Sep 13, 2001 at 09:48:27PM -0400, Dan Sugalski wrote:
> Ah, I'm sure it was a slip 'o the keyboard. :) config.h_in (or config_h.in)
> are both OK, and unique enough on 8.3 systems.
Yeah, that was it! Brent, do you want to take care of that.
(config_h.in would be better, since it gets min
On Thu, Sep 13, 2001 at 06:35:39PM -0700, Brent Dax wrote:
> Ask Simon, he's the one who came up with 'config.h.in' in the first
> place.
Oops. Naughty me.
I always fancied doing things like "config.hh" for .h file templates,
but then C++ people might get confused.
Brent Dax:
# Sent: Thursday, September 13, 2001 14:17
# To: Simon Cozens; [EMAIL PROTECTED]
# Subject: RE: Things we need to do.
#
#
# Simon Cozens:
# # 2) Extend the Configure.pl system to autogenerate the
# #Makefile as well. Use Makefile.in as a template, and
# #fill in
If you're looking for something to do, we *always* have good
little jobs for people. :)
1) See if there's a neat way of making the assembler
grok shortened forms of ops:
add I1, I2, I3 => add_i I1, I2, I3
print S1 => print_s S1
2) Extend the Configure.pl syste
