On Mon, Jun 29, 2009 at 04:58:04PM +0100, Dagfinn Ilmari Mannsåker wrote:
> Jarkko Hietaniemi <j...@iki.fi> writes:
>
> > On Mon, Jun 29, 2009 at 11:41 AM, Abigail<abig...@abigail.be> wrote:
> >> On Fri, Jun 26, 2009 at 02:46:36PM +0200, H.Merijn Brand wrote:
> >>>
> >>> WTF, where on earth did you read that a space is not allowed before an
> >>> opening paren on an aggregate function? All other databases I've seen
> >>> so far, including SQLite and DBD::CSV allow it. You moron!
> >>
> >> MySQL, the Perl6 of databases.
> >
> > That's unfair, at least MySQL has had several product releases already.
>
> Don't let chromatic hear you say that, they've had 17 "stable" releases
> already! Never mind that it only passes 68% of the spectests (which
> cover an uknown proportion of the spec (which is an unknown proportion
> complete)) and can apparently only be run from the build directory.
The parrot binary itself could be run successfully from an installed version
with the build tree removed as of the release one month before the release
numbered 1.0
Rakudo does not (yet) build against an installed parrot, and the "perl6"
executable will stop working if the parrot build tree is removed:
$ ./perl6
./perl6: error while loading shared libraries: libparrot.so.1.3.0: cannot
open shared object file: No such file or directory
Unlike chromatic, the people actually working on Rakudo itself (and I am not
one of them) do not use the word "stable", do acknowledge that it can't yet
be installed, and do not use any terms that might give the impression that
it is any way near ready. (But do publicise the numbers for the spectests)
I'm not sure if the fact that you can't install it makes it less hateful,
because it means you can't actually use it for real work yet, and hence
subsequently find that using it was a mistake.
Nicholas Clark
