Simon Glover <[EMAIL PROTECTED]> wrote:
> ..., but I'm posting it to the list rather than simply applying it
> because it is not clear to me that the behaviour described above is
> precisely what we want.
We have to precisely define what should happen with these corner cases.
We should impleme
Peter Christopher <[EMAIL PROTECTED]> wrote:
> I'll check out the build scripts and see what flags will do to compile
> the t/src/*.c and put them in. Further, I'll try to determine good
> values for --cflags, --include, etc. from the Makefile.
Ok. Can you move the build script to F and provide a
Perl 6 Summary for 2004-01-03 through 2004-01-11
Welcome to another Perl 6 summary. In this summary, we will explore such
thrilling issues as multi-dimensional slices of Chinese food. After all,
the amount of sauce any piece of Chinese food can absorb is proportional
to its surface
Hi Listers,
Last I checked (which was moments ago) it was either (a)
impossible to, or (b) I couldn't figure out how to, search the parrot
mailing list archive. I.e. I can't search
www.nntp.perl.org/group/perl.perl6.internals
for key words. Could someone give me the heads up on how to
Hi again Listers,
Ok it looks like to me that the ./blib directory is associated
in some way with the ./icu directory [same header files, vague
references to blib from icu README, etc.]. The (installation) MANIFEST
never mentions blib but installs icu. BUT cc_inc [of the build process
fame
On Jan-11, Peter Christopher wrote:
>
> Last I checked (which was moments ago) it was either (a)
> impossible to, or (b) I couldn't figure out how to, search the parrot
> mailing list archive. I.e. I can't search
> www.nntp.perl.org/group/perl.perl6.internals
> for key words. Could someo
