headers
The Perl 6 Summarizer | 8 Mar 2004 23:41
Picon

This week's summary

The Perl 6 Summary for the week ending 2004-03-07
    Time marches on, and another summary gets written, sure as eggs are eggs
    and chromatic is a chap with whom I will never start a sentence. We
    start, as always, with perl6-internals.

  Platform games
    Work continued this week on expanding the number of known (and
    preferably known good) platforms in the PLATFORMS file.

  Languages tests
    Dan reckons it's time to be a little more aggressive with tests for
    ancillary stuff, in particular the contents of the languages
    subdirectory. He called for language maintainers (and any other
    interested parties) to at least get minimal tests written for all the
    languages in the languages directory, and to get those welded to the
    "languages-test" makefile target.

    http://tinyurl.com/24sd3

  IMCC and objects/methods
    Tim Bunce congratulated everyone on Parrot 0.1.0 before asking about
    where we stood with IMCC and objects/methods. Leo confirmed Tim's
    supposition that there is no syntactic support for objects and methods
    in IMCC, at least in part because there's been no discussion of how such
    syntax should look.

    http://tinyurl.com/2jerk

  Parrotbug reaches 0.0.1
    Jerome Quelin responded to Dan's otherwise ignored request for a parrot
(Continue reading)

Permalink | Reply | 0 comments |
headers
The Perl 6 Summarizer | 16 Mar 2004 18:12
Picon

This week's summary

The Perl 6 Summary for the week ending 2004-03-14
    Another week, another summary. It's been a pretty active week so, with a
    cunningly mixed metaphor, we'll dive straight into the hive of activity
    that is perl6-internals.

  Benchmarking
    Discussion and development of Sebastien Riedel's nifty Parrot
    comparative benchmarking script continued. Leo suggested a handy config
    file approach which would allow for adding benchmarks in other languages
    without having to change the script itself.

    The initial results don't look good if you're name's Dan and you want to
    avoid getting a pie in the face at OSCON though, as Dan pointed out,
    there's a few tricks still to be played in this area. Anyway,
    benchmark.pl is now in the CVS tree if you want to play with it.

    http://tinyurl.com/2h7c4

  Speeling mistacks
    The ever helpful chromatic applied Bernhard Schmalhofer's patch to fix
    up an endemic speling mostake in some tests. Apparently DESCRIPTION
    isn't spelt "DECSRIPTION".

    http://tinyurl.com/3dd85

  Dates and Times
    Discussion of parrot's handling of dates and times continued this week
    too. Joshua Hoblitt who works on DateTime.pm (a very handy base for
    doing date/time handling in Perl 5, you should check it out) said that
    the DateTime people really, really want is "an epoch that's *absolutely*
(Continue reading)

Permalink | Reply | 0 comments |
headers
The Perl 6 Summarizer | 29 Mar 2004 18:16
Picon

This week's summary

The Perl 6 Summary for the week ending 2004-03-28
    ... and we're back! Another interesting week in Perl 6. Your Summarizer
    even wrote some [parrot] code and it's been simply ages since he did
    that. In accordance with ancient custom, we'll start the summary with
    perl6-internals.

  Building with miniparrot
    Back in the early days Dan proposed, and it was generally agreed that
    the Parrot build process wouldn't be Perl dependent, but instead there
    would be a few OS specific 'bootstrap' scripts, enough to get miniparrot
    up and running. Miniparrot would have just enough smarts to be able to
    complete the configuration and build the final full parrot.

    After last week's discussion about reinventing metaconfig, I wondered if
    the miniparrot plan was still in place. It seems I'd missed the
    discussion of "stat" that ended up talking about how miniparrot would be
    able to do its job. I find myself wondering what else is needed to get
    miniparrot to the point where it can start doing configuration work.

    http://tinyurl.com/2djx8

  Continuations continued (and fun with stacks)
    Warning: The following discussion of the Continuation discussions is
    irrevocably biased; I find it very hard to be objective about
    discussions I participate in, and I was rather loud mouthed in this one.

    The previous discussions of the uses and semantics of continuations
    carried over into this week. Piers Cawley argued that the current stack
    architecture seemed to be optimized for the wrong thing, with the
    special case RetContinuations being symptoms. He argued that current
(Continue reading)

Permalink | Reply | 0 comments |

Gmane