perl.perl6.build...Re: Configurators! by Andy Dougherty- August 30, 2001 On Sun, 26 Aug 2001, Nathan Torkington wrote:> We&39;re about to have a tarball of basic interpreter source (no compiler> yet, only an assembler). Dan&39;s already run into portability problems,> and once it comes out we&39;re going to need to start working on the> configuration and build system.Could you give some examplesFor the time being, it might be useful to use the existing perl5installation to bootstrap the perl6 build somehow. Medium and long term,that&39;s a really...http://www.nntp.perl.org/group/perl.perl6.build/2001/08/msg15.html Configurators! by Nathan Torkington- August 27, 2001 We&39;re about to have a tarball of basic interpreter source (no compileryet, only an assembler). Dan&39;s already run into portability problems,and once it comes out we&39;re going to need to start working on theconfiguration and build system.Jarkko, are you still interested in leading this (I&39;m unsure when jhireturns from holiday, so don&39;t take it as a &39;no&39; if there&39;s not animmediate response).Nathttp://www.nntp.perl.org/group/perl.perl6.build/2001/08/msg14.html Modules, Versioning, and Beyond by Hildo.Biersma- August 2, 2001 >>>>> "Bryan" == Bryan C Warnock <bwarnockcapita.com> writes:Bryan> Using Multiple Versions Of The Same Module In One ProgramBryan> There are a lot of reasons why this isn&39;t a good idea, or evenBryan> possible in places. Non-Perl code on the backend, forBryan> instance, will probably prevent multiple versions from beingBryan> linked in. But since we&39;re doing more and more in Perl, I&39;llBryan> bring it up. If you are already convinced...http://www.nntp.perl.org/group/perl.perl6.build/2001/08/msg13.html |