Perl 6 Summary for 2005-01-31 through 2004-02-8
    All~

    Welcome to yet another summary in which I will undoubtedly confuse to
    homophones. Probably more than a few this week as I am a little tired.
    But perhaps the alien on my window or the vampire on my monitor will
    help straighten it all out.

  Perl 6 Language
   autothreading generalization
    Luke Palmer's thread about auto-threading seems to have wound down
    without much resolution, or at the very least without a syntax that I
    like.

    <http://xrl.us/e26z>

   Featherweight Perl6
    Autrijus Tang introduced Featherweight Perl6, a side-effect-free subset
    of Perl6. FP6 is the first step on a journey for Pugs to conquer the
    world.

    <http://xrl.us/e262>

   Value Types vs Implementation Types
    Autrijus Tang in his work on FP6 became confused by types. He asked some
    questions about Types on perl 6 language and was apparently told to go
    to perl 6 compilers. From perl 6 compilers, he was told he should really
    be on perl 6 language. Sorry for the run around, the proper place for
    questions about language semantics is perl 6 language as he originally
    posted. Eventually all of that was settled and he even got his question
    answered.

    <http://xrl.us/e263> -- original post

    <http://xrl.us/e264> -- retry with less compiler speak

   Logic Programming in Perl 6
    Ovid asked what logic programming in perl 6 would look like. No answer
    yet, but I suppose I can pick the low hanging fruit: as a limiting case
    you could always back out the entire perl 6 grammar and insert that of
    prolog.

    <http://xrl.us/e265>

   the leaning tower of numbers
    Autrijus Tang asked what sort of number tower Perl6 had. He was planning
    (and implemented) that of Scheme until he gets an answer.

    <http://xrl.us/e266>

   some quick questions
    Autrijus Tang asked a few questions about operators in specific
    contexts. He got a few answers, although I don't think he got them all.

    <http://xrl.us/e267>

   getopt::signature
    Juerd wants to be able to give his script a general signature which
    magically parses command line arguments. Many people thought it was a
    cool idea that should be provided as a module rather than in the core.
    This led to talk about creating a signature object which could be passed
    to this module so that it doesn't need macros. Sounds good to me.

    <http://xrl.us/e268>

   S03 inconsistency
    Juerd found a knit to pick. No comment about whether to pick the first
    or second option though...

    <http://xrl.us/e269>

   regex precedence
    Nicholas Clark wondered about adding a little operator precedence to
    regexes so that people could avoid a few common problems. Sounds like a
    good idea to me...

    <http://xrl.us/e27a>

   pipe dreams
    Juerd wondered if he could mix = and ==> in a sane way. The answer
    appears to be no. Once you bring in ==> you should stick with it.

    <http://xrl.us/e27b>

   4 < $x < 2 == true?!?
    Autrijus Tang wondered how junctions and chained comparators worked. He
    found that under certain semantics, one can receive very troubling
    answers. Larry agreed with Autrijus that the unintuitive semantics
    should be avoided.

    <http://xrl.us/e27c>

  Perl 6 Compilers
   Pugs 6.0.0
    Autrijus Tang released Pugs 6.0.0. It has many cool features and was
    created in only 6 days. A testament to the power of Haskel or the
    caffeine intake of Autrijus. (Although to be fair he skipped more
    version numbers then Java did in its jump to 5.0...)

    <http://xrl.us/e27d> -- anouncement

    <http://autrijus.org/pugs/> -- pugs website
    <http://use.perl.org/~autrijus/journal/> -- implementation journal

  Parrot
   gdbmhash warning
    Bernhard Schmalhofer fix a problem where gdbmhash could make configure
    produce a warning. Leo applied it.

    <http://xrl.us/e27e>

   PyNCI
    Sam and Leo worked out the correct way to create NCI methods for Python.
    Leo ended by proposing a table to assist Parrot based on the current
    language, no answer to that idea...

    <http://xrl.us/e27f>

   makefile cleanup
    Bernhard Schmalhofer cleaned up some of the makefiles and configure
    system. Leo applied the patch.

    <http://xrl.us/e27g>

   ParrotIOLayer* const or not
    François Perrad provided a patch making the ParrotIOLayer* const in the
    API. Leo applied it, but Melvin warned that while this may be safe now,
    the API intended to allow mutability. I think for the moment it is still
    in though...

    <http://xrl.us/e27h>

   Win32 Parrot
    Ron Blaschke helped Parrot back onto its feet in the windows world.

    <http://xrl.us/e27i>

    <http://xrl.us/e27j>

    <http://xrl.us/e27k>

    <http://xrl.us/e27m>

    <http://xrl.us/e27n>

    <http://xrl.us/e27o>

    <http://xrl.us/e27p> -- latest results

   Parrot_load_bytecode failure?
    Ian Joyce wondered what would happen if Parrot_load_bytecode failed. The
    answer: exception.

    <http://xrl.us/e27q>

   reading past EOF
    Matt Diephouse was annoyed that reading past EOF gave an unhelpful error
    message. Leo fixed it.

    <http://xrl.us/e27r>

   FreeBSD build problems
    Will Coleda found a build problem for parrot on FreeBSD. Adriano
    Ferreira provided a work around, but the build system needs to be
    smarter too. On a side note, I want a picture of the BSD daemon (pitch
    fork included) with a pirate hat, an eye patch, and a parrot on its
    shoulder.

    <http://xrl.us/e27s>

   gmake requirement?
    There was some confusion about what does and does not require gmake on
    FreeBSD. IMCC does not. ICU does. Fortunately, with Dan's string stuff
    ICU will become optional and so we won't require it.

    <http://xrl.us/e27t>

   locate_runtime_file with absolute paths
    Jeff Horwitz notices that Parrot_locate_runtime_file could segfault when
    playing with an absolute path. He put some work in to fix it.

    <http://xrl.us/e27u>

   expected vpm.imc output error
    Bernhard Schmalhofer fixed a failing benchmark test which just had
    slightly wrong output expectations. chromatic (whose uncapitalized name
    does not bother me) applied the patch.

    <http://xrl.us/e27v>

   subvercive parrot
    Ron Blaschke asked if Parrot was planning to move to SVN. Many argument
    in favor; few argued against. No word from the powers that be.

    <http://xrl.us/e27w>

   Parrot 0.1.2?
    Will Coleda wondered if the time for Parrot 0.1.2 was growing close. Leo
    pointed out some things that need to be fixed. Honestly, the real
    impetement is that we do not yet have a cool code name for it. I suggest
    kiwi, because everyone knows they really want to be parrots.

    <http://xrl.us/e27x>

   making an array out of an undef
    Ron Blaschke was surprised when an operation was quitely turning an
    Undef into an array. Leo explained to him that this set of semantics was
    known and expected.

    <http://xrl.us/e27y>

   solaris issues
    Andy Dougherty notices that parrot was failing some tests on solaris. He
    tried to provide enough info for people to help him, but no one did.

    <http://xrl.us/e27z>

   Linux PPC issues
    Jeff Dik posted a patch that worked around a problem on Linux PPC.
    chromatic pointed out that there was a more correct patch already in RT.
    Jeff Dik slapped himself on the forehead and reminded himself to check
    RT first.

    <http://xrl.us/e272>

  The usual footer
    Posting via the google groups interface does not work. To post to any of
    these mailing lists please subscribe by sending email to
    <[EMAIL PROTECTED]>,
    <[EMAIL PROTECTED]>, or
    <[EMAIL PROTECTED]>. If you find these summaries useful
    or enjoyable, please consider contributing to the Perl Foundation to
    help support the development of Perl. You might also like to send
    feedback to [EMAIL PROTECTED]

    <http://donate.perl-foundation.org/> -- The Perl Foundation
    <http://dev.perl.org/perl6/> -- Perl 6 Development site
    <http://planet.parrotcode.org/> -- Parrot Blog aggregator

Reply via email to