Re: I need to run and release a program in the background
On 2020-11-16 15:50, Andy Bach wrote: > this command runs OUTSIDE the shell. There are no environmental variables to be found such as $HOME Well, not exactly none, but a limited env $ raku -e 'my $pA = Proc::Async.new( "env" ); $pA.start;' ... Hi Andy, Limited indeed! I get around it with: my Str $Leafpadrc = $*HOME ~ "/" ~ ".config/leafpad/leafpadrc"; :-) -T
Re: I need to run and release a program in the background
> this command runs OUTSIDE the shell. There are no environmental variables
> to be found such as $HOME
Well, not exactly none, but a limited env
$ raku -e 'my $pA = Proc::Async.new( "env" ); $pA.start;'
TERM=xterm
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_TYPE=tty
LESSCLOSE=/usr/bin/lesspipe %s %s
COMP_WORDBREAKS=
"'><;|&(:
LANG=en_US.UTF-8
SSH_CLIENT=10.222.64.247 65064 22
SHLVL=1
GOARCH=386
XDG_DATA_DIRS=/home/andy/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
USER=andy
SSH_TTY=/dev/pts/1
XDG_SESSION_CLASS=user
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
GOROOT=/home/andy/go
LOGNAME=andy
MOTD_SHOWN=pam
LESSOPEN=| /usr/bin/lesspipe %s
GOBIN=/home/andy/bin
_=/usr/bin/perl6
HOME=/home/andy
PWD=/home/andy
XDG_SESSION_ID=596
SHELL=/bin/bash
GOOS=linux
SSH_CONNECTION=10.222.64.247 65064 156.126.45.100 22
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
From: ToddAndMargo via perl6-users
Sent: Monday, November 16, 2020 4:39 PM
To: perl6-users@perl.org
Subject: Re: I need to run and release a program in the background
CAUTION - EXTERNAL:
On 2020-11-14 12:23, ToddAndMargo via perl6-users wrote:
> Hi All,
>
> How do I use qqx or other to run and release a
> program in the background, like bash's "&"?
>
> Many thanks,
> -T
>
My revised keeper:
How to run and release a file:
Note: this command runs OUTSIDE the shell. There are no
environmental variables to be found such as $HOME
the parameters are in quotes, including the name of
the program to run, just like `run`
$ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad" ); my $promise =
$pA.start; await $promise;'
$ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad" ); $pA.start;'
$ p6 'my $pA = Proc::Async.new( '/usr/bin/leafpad
"/home/linuxutil/XferParts.pl6.tmp"' ); $pA.start;'
To get this to run with the shell, call "bash -c".
Note: all the parameters to the command bash executing
with "-c" go into an embedded quote stream.
For example:
'/usr/bin/leafpad "/home/linuxutil/XferParts.pl6.tmp"'
my $pA = Proc::Async.new( "bash", "-c", '/usr/bin/leafpad
"/home/linuxutil/XferParts.pl6.tmp"' );
say $pA;
$pA.start;
Proc::Async.new(path => "bash", args => ["-c", "/usr/bin/leafpad
\"/home/linuxutil/XferParts.pl6.tmp\""], command => ("bash", "-c",
"/usr/bin/leafpad \"/home/linuxutil/XferParts.pl6.tmp\""), w => Any,
enc => "utf8", translate-nl => Bool::True, win-verbatim-args =>
Bool::False, started => Bool::False)
CAUTION - EXTERNAL EMAIL: This email originated outside the Judiciary. Exercise
caution when opening attachments or clicking on links.
Re: I need to run and release a program in the background
On 2020-11-14 12:23, ToddAndMargo via perl6-users wrote:
Hi All,
How do I use qqx or other to run and release a
program in the background, like bash's "&"?
Many thanks,
-T
My revised keeper:
How to run and release a file:
Note: this command runs OUTSIDE the shell. There are no
environmental variables to be found such as $HOME
the parameters are in quotes, including the name of
the program to run, just like `run`
$ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad" ); my $promise =
$pA.start; await $promise;'
$ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad" ); $pA.start;'
$ p6 'my $pA = Proc::Async.new( '/usr/bin/leafpad
"/home/linuxutil/XferParts.pl6.tmp"' ); $pA.start;'
To get this to run with the shell, call "bash -c".
Note: all the parameters to the command bash executing
with "-c" go into an embedded quote stream.
For example:
'/usr/bin/leafpad "/home/linuxutil/XferParts.pl6.tmp"'
my $pA = Proc::Async.new( "bash", "-c", '/usr/bin/leafpad
"/home/linuxutil/XferParts.pl6.tmp"' );
say $pA;
$pA.start;
Proc::Async.new(path => "bash", args => ["-c", "/usr/bin/leafpad
\"/home/linuxutil/XferParts.pl6.tmp\""], command => ("bash", "-c",
"/usr/bin/leafpad \"/home/linuxutil/XferParts.pl6.tmp\""), w => Any,
enc => "utf8", translate-nl => Bool::True, win-verbatim-args =>
Bool::False, started => Bool::False)
Re: I need to run and release a program in the background
On 2020-11-14 13:14, ToddAndMargo via perl6-users wrote: On 2020-11-14 12:23, ToddAndMargo via perl6-users wrote: Hi All, How do I use qqx or other to run and release a program in the background, like bash's "&"? Many thanks, -T The guys on hte chat line figured it out for me: $ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad" ); my $promise = $pA.start;' My keeper on the subject: How to run and release a file: Note: this command runs OUTSIDE the shell. There are no environmental variables to be found such as $HOME the parpameters are in quotes, including the name of the program to run, just like `run` $ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad" ); my $promise = $pA.start; await $promise;' $ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad" ); $pA.start;' $ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad", "/home/linuxutil/XferParts.pl6.tmp" ); $pA.start;' To get this to run with the shell, call "bash -c" my $pA = Proc::Async.new( "bash", "-c", "/usr/bin/leafpad /home/linuxutil/XferParts.pl6.tmp" ); $pA.start;
Re: I need to run and release a program in the background
On 2020-11-14 12:23, ToddAndMargo via perl6-users wrote: Hi All, How do I use qqx or other to run and release a program in the background, like bash's "&"? Many thanks, -T The guys on hte chat line figured it out for me: $ p6 'my $pA = Proc::Async.new( "/usr/bin/leafpad" ); my $promise = $pA.start;'
I need to run and release a program in the background
Hi All, How do I use qqx or other to run and release a program in the background, like bash's "&"? Many thanks, -T -- A computer without Microsoft is like a chocolate cake without the mustard
Announce: Rakudo Star Release 2018.10
Announce: Rakudo Star Release 2018.10 A useful and usable production
distribution of Rakudo Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the October 2018 release of "Rakudo Star", a useful and usable
production distribution of Rakudo. The tarball for this release is
available from https://rakudo.perl6.org/downloads/star/.
Binaries for macOS and Windows (64 bit) are also available at the same
location.
This is a post-Christmas (production) release of Rakudo Star and implements
Perl v6.c. It comes with support for the MoarVM backend (all module tests
pass on supported platforms). Currently, Star is on a quarterly release
cycle.
Please note that this release of Rakudo Star is not fully functional with
the JVM backend from the Rakudo compiler. Please use the MoarVM backend
only.
We make a distinction between the language ("Perl 6" or "Raku") and
specific implementations of the language such as "Rakudo".
This Star release includes release 2018.10
<https://raw.githubusercontent.com/rakudo/rakudo/2018.10/docs/announce/2018.10.md>
of the Rakudo compiler <http://github.com/rakudo/rakudo>, version 2018.10
MoarVM <http://moarvm.org/>, plus various modules, documentation, and other
resources collected from the community.
The Rakudo compiler changes since the last Rakudo Star release are now
listed in "2018.08.md" and 2018.09.md" under the "rakudo/docs/announce"
directory of the source distribution.
This is the first Rakudo Star release that comes with an additional JS
backend. See 6pad project at https://perl6.github.io/6pad/ for running
Perl 6 code directly in your browser.
Important Rakudo bug fixes are now listed at https://alerts.perl6.org/
Also see Rakudo Star errata at https://perl6.org/downloads/
Deprecation:
- LWP::Simple is deprecated and will be removed. Please use
"HTTP::UserAgent".
- panda-sub which pointed user to zef now removed.
Notable changes in modules shipped with Rakudo Star:
- openssl: Bump version 0.1.21.
- tap-harness6: Bump version to 0.0.4 for coloring
- zef: version 0.5.3
There are some key features of Perl 6 that Rakudo Star does not yet handle
appropriately, although they will appear in upcoming releases. Some of the
not-quite-there features include:
- advanced macros
- some bits of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features that
lists the known implemented and missing features of Rakudo's backends and
other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many that
we've missed. Bug reports about missing and broken features are welcomed at
rakudo...@perl.org.
See https://perl6.org/ for links to much more information, including
documentation, example code, tutorials, presentations, reference materials,
design documents, and other supporting resources. Tutorials are available
under the "docs" directory in the release tarball.
The development team thanks all of the contributors and sponsors for making
Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org mailing
list, or join us on IRC #perl6 on freenode.
--
Steve Mynott
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
Announce: Rakudo Star Release 2018.06
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce
the June 2018 release of "Rakudo Star", a useful and usable production
distribution of Rakudo Perl 6. The tarball for this release is available from
<https://rakudo.perl6.org/downloads/star/>.
Binaries for macOS and Windows (64 bit) are also available at the same
location.
This is a post-Christmas (production) release of Rakudo Star and implements
Perl v6.c. It comes with support for the MoarVM backend (all module tests pass
on supported platforms). Currently, Star is on a quarterly release cycle.
Please note that this release of Rakudo Star is not fully functional with the
JVM backend from the Rakudo compiler. Please use the MoarVM backend only.
In the Perl 6 world, we make a distinction between the language ("Perl 6") and
specific implementations of the language such as "Rakudo Perl 6".
This Star release includes [release 2018.06] of the [Rakudo Perl 6 compiler],
version 2018.06 [MoarVM], plus various modules, documentation, and other
resources collected from the Perl 6 community.
[release 2018.06]:
https://raw.githubusercontent.com/rakudo/rakudo/2018.06/docs/announce/2018.06.md
[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo
[MoarVM]: http://moarvm.org/
The Rakudo compiler changes since the last Rakudo Star release are now listed
in "2018.05.md" and 2018.06.md" under the "rakudo/docs/announce" directory of
the source distribution.
Important Rakudo bug fixes are now listed at <https://alerts.perl6.org/>
Also see Rakudo Star errata at <https://perl6.org/downloads/>
Deprecation:
* LWP::Simple is deprecated and will be removed. Please use "HTTP::UserAgent".
Notable changes in modules shipped with Rakudo Star:
* openssl: added
* io-socket-ssl: added
* http-useragent: version 1.1.44
* Terminal-ANSIColor: italic now accessible via the color() sub
* zef: version 0.4.5
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* some bits of Synopsis 9 and 11
There is an online resource at <http://perl6.org/compilers/features>
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at .
See <https://perl6.org/> for links to much more information about
Perl 6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
<http://rakudo.org/how-to-help>, ask on the
mailing list, or join us on IRC \#perl6 on freenode.
--
Steve Mynott
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
Announce: Rakudo Star Release 2018.04
# Announce: Rakudo Star Release 2018.04
## A useful and usable production distribution of Rakudo Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce
the April 2018 release of "Rakudo Star", a useful and usable production
distribution of Rakudo Perl 6. The tarball for this release is available
from
<https://rakudo.perl6.org/downloads/star/>.
Binaries for macOS and Windows (64 bit) are also available at the same
location.
This is a post-Christmas (production) release of Rakudo Star and implements
Perl v6.c. It comes with support for the MoarVM backend (all module tests
pass
on supported platforms). Currently, Star is on a quarterly release cycle.
Please note that this release of Rakudo Star is not fully functional with
the
JVM backend from the Rakudo compiler. Please use the MoarVM backend only.
In the Perl 6 world, we make a distinction between the language ("Perl 6")
and
specific implementations of the language such as "Rakudo Perl 6".
This Star release includes [release 2018.04.1] of the [Rakudo Perl 6
compiler],
version 2018.04.1 [MoarVM], plus various modules, documentation, and other
resources collected from the Perl 6 community.
[release 2018.04.1]:
https://raw.githubusercontent.com/rakudo/rakudo/2018.04.1/docs/announce/2018.04.1.md
[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo
[MoarVM]: http://moarvm.org/
The Rakudo compiler changes since the last Rakudo Star release of 2017.10
are
now listed in "2018.02.md", "2018.03.md", "2018.04.md" and 2018.04.1.md"
under
the "rakudo/docs/announce" directory of the source distribution.
Important Rakudo bug fixes are now listed at
[Perl 6 Alerts]: https://alerts.perl6.org/
Deprecation:
+ "panda" has been removed from releases after 2017.10 since it is
deprecated. Please use "zef".
+ LWP::Simple is deprecated and will be removed. Please use
"HTTP::UserAgent".
Notable changes in modules shipped with Rakudo Star:
+ datetime-parse: Update asctime parsing
+ doc: Too many to list including jjmerelo TPF Grant Work.
+ http-useragent: Pre-allocate a buffer when getting content
+ json\_fast: Unescape fixes.
+ jsonrpc: LWP::Simple replaced with HTTP::UserAgent.
+ svg-plot: Fix xy-line plot closing over some variables it shouldn't.
+ zef: version 0.3.1 (includes fix for space in home directory)
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* some bits of Synopsis 9 and 11
There is an online resource at <http://perl6.org/compilers/features>
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at <rakudo...@perl.org>.
See <https://perl6.org/> for links to much more information about
Perl 6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
<http://rakudo.org/how-to-help>, ask on the <perl6-compi...@perl.org>
mailing list, or join us on IRC \#perl6 on freenode.
--
Steve Mynott <steve.myn...@gmail.com>
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
Re: Announce: Rakudo Star Release 2018.01
On 01/29/2018 07:31 AM, Steve Mynott wrote: Binaries for macOS and Windows (64 bit) will shortly be available at the same location. And sign of 32 bit for Windows in our future?
Announce: Rakudo Star Release 2018.01
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the January 2018 release of "Rakudo Star", a useful and
usable production distribution of Rakudo Perl 6. The tarball for this
release is available from https://rakudo.perl6.org/downloads/star/.
Binaries for macOS and Windows (64 bit) will shortly be available at
the same location.
This is a post-Christmas (production) release of Rakudo Star and
implements Perl v6.c. It comes with support for the MoarVM backend
(all module tests pass on supported platforms). Currently, Star is on
a quarterly release cycle.
Please note that this release of Rakudo Star is not fully functional
with the JVM backend from the Rakudo compiler. Please use the MoarVM
backend only.
In the Perl 6 world, we make a distinction between the language ("Perl
6") and specific implementations of the language such as "Rakudo Perl
6".
This Star release includes release 2018.01 of the Rakudo Perl 6
compiler, version 2018.01 MoarVM, plus various modules, documentation,
and other resources collected from the Perl 6 community.
The Rakudo compiler changes since the last Rakudo Star release of
2017.10 are now listed in "2017.11.md", "2017.12.md", and "2018.01.md"
under the "rakudo/docs/announce" directory of the source distribution.
Important Rakudo bug fixes are now listed at [Perl 6 Alerts]:
https://alerts.perl6.org/
Deprecation:
+ "panda" has been removed from releases after 2017.10 since it is
deprecated. Please use "zef".
+ LWP::Simple is deprecated and will be removed. Please use "HTTP::UserAgent".
Notable changes in modules shipped with Rakudo Star:
+ JSON-Class: Alter the way in which the re-exporting of the traits works
+ JSON-Marshal: Fix for associative and positional type objects
+ Pod-To-HTML: Document P6DOC\_DEBUG
+ datetime-parse: New. Dependency of http-useragent
+ doc: Too many to list.
+ http-useragent: New. Intended as replacement for LWP::Simple (now deprecated)
+ json\_fast: fix off-by-one in treacherous escape detection
+ perl6-lwp-simple: HTML header names with mixed case fix
+ svg: Fix example in README
+ tap-harness6: Make TAP parsing loose by default before rakudo
2017.09 in prove too
+ zef: Warns about missing META6.json. Sort "list" output.
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
+ advanced macros
+ some bits of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See https://perl6.org/ for links to much more information about Perl
6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in the
release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC #perl6 on freenode.
--
Steve Mynott <steve.myn...@gmail.com>
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
Announce: Rakudo Star Release 2017.10
A useful and usable production distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the October 2017 release of "Rakudo Star", a useful and
usable production distribution of Perl 6. The tarball for this release
is available from https://rakudo.perl6.org/downloads/star/.
Binaries for macOS and Windows (64 bit) are also available at the same location.
This is a post-Christmas (production) release of Rakudo Star and
implements Perl v6.c. It comes with support for the MoarVM backend
(all module tests pass on supported platforms). Currently, Star is on
a quarterly release cycle.
IMPORTANT: "panda" has been removed from this release since it is
deprecated. Please use "zef" instead.
Please note that this release of Rakudo Star is not fully functional
with the JVM backend from the Rakudo compiler. Please use the MoarVM
backend only.
In the Perl 6 world, we make a distinction between the language ("Perl
6") and specific implementations of the language such as "Rakudo
Perl".
This Star release includes release 2017.10 of the Rakudo Perl 6
compiler, version 2017.10 MoarVM, plus various modules, documentation,
and other resources collected from the Perl 6 community.
The Rakudo compiler changes since the last Rakudo Star release of
2017.07 are now listed in "2017.08.md", "2017.09.md", and "2017.10.md"
under the "rakudo/docs/announce" directory of the source distribution.
Notable changes in modules shipped with Rakudo Star:
+ DBIish: Newer version (doesn't work with 2017.01 anymore)
+ Test-META: New. also dependencies (JSON-Class, JSON-Marshal,
JSON-Name, JSON-Unmarshal and META6)
+ doc: Too many to list. p6doc-index merged into p6doc and index built
on first run.
+ p6-Template-Mustache: Fixed on Windows.
+ panda: Removed. Stub added to warn about this.
+ perl6-datetime-format: New (heavily used in ecosystem)
+ perl6-file-which: Fixed tests on Windows
+ tap-harness6: Many fixes.
+ zef: New version with many fixes
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
advanced macros
non-blocking I/O (now works for sockets and process)
some bits of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See https://perl6.org/ for links to much more information about Perl
6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in the
release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC #perl6 on freenode.
--
4096R/EA75174B Steve Mynott <steve.myn...@gmail.com>
Re: Announce: Rakudo Star Release 2017.07
On 07/25/2017 12:30 AM, Elizabeth Mattijsen wrote: What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler release with a set of useful modules added (“batteries included”). https://rakudo.perl6.org/downloads/star/ vs https://rakudo.perl6.org/downloads/rakudo/ And to add insult Fedora only supports Rakudo
Re: Announce: Rakudo Star Release 2017.07
TL;DR Imo, one of Perl 6's notable strengths is its approach to its specification. Imo companies will love it. I can see it becoming a primary tool for driving P6 forward in just the right way. Steve has already answered with the short version of some of what I say below, and I agree with what you (Darren) said in your reply to him. So perhaps this is more for ToddAndMargo or other readers. >From the start in 2000, Larry intended that the P6 project would distinguish between various distinct notions of "specification": * An evolving set of English documents that would be used to guide compiler developers attempting to write a compiler that implements that "specification". For the last few years P6 project leaders have been calling these "Design Documents". The latest/last versions of these are stored at design.perl6.org. They are now largely an historical footnote -- calling these or any other English language documents a "specification" was explicitly deprecated some years ago. * An evolving set of English documents that would be used to guide end users attempting to understand or write P6 code. Aka end user documentation. The latest version of this is stored at doc.perl6.org. Contributors can draw insight from the design documents (as per previous bullet point) but are supposed to focus on the only remaining specification (as per the next bullet point). * An evolving Executable specification that emerges from that effort. A compiler **must** match **100%** of this executable specification if the compiler is to be officially allowed to claim it implements that specification. This is what the 6.c specification is and what the 6.d specification will be. * The 6.c specification is stored at https://github.com/perl6/roast/tree/6.c (Maybe we should change the description from "Perl 6 test suite" to "Perl 6 language specification".) There's also a 6.c errata at https://github.com/perl6/roast/tree/6.c-errata which, aiui, is what the monthly Rakudo releases target. So, anything you read in English, like "doesn't yet implement macros" is... written in English and is not part of a Perl 6 language specification, per contemporary P6 usage of the word "specification". > So I think it is reasonable for Rakudo to actually implement ALL of 6.c > before too long, that it would catch up, and otherwise the intent is that > Rakudo would be leading on things that eventually become 6.d etc later. Aiui Rakudo's HEAD implemented all of 6.c (on at least one platform) as of December 25th 2015 and each subsequent monthly release has as well. (Well, actually, all of 6.c.errata.) In principle this is an excellent foundation for manageable (in tech and business senses), systematic, community driven, compiler dev mediated, language stability, backwards compatibility, and evolution. If someone (or some company) wants to drive the language forward, then they work with the community to propose changes to the test suite for 6.d or some later 6.* version. These changes test that the particular features they want are working. Community members can do things like attaching a time-limited incentive for compiler devs to alter the compiler to pass some particular set of new tests. Indeed, I imagine it would be fairly easy to set up a flow of direct micro-funding of whatever a given community participant considers more important to them. If it's backwards compatibility, then write tests that ensure that backwards compatibility if they haven't already been written and/or add incentives to currently failing/skipped tests. A similar approach applies for those wanting more test coverage of existing features, or new features. -- raiph On Tue, Jul 25, 2017 at 11:23 AM, Darren Duncan <dar...@darrenduncan.net> wrote: > There's a key difference however. > > While programming languages continue to evolve, the expectation is that a > production-complete Rakudo would always be a functional superset (or equal > to) the Perl 6 language specification which is current at the time. > > So I think it is reasonable for Rakudo to actually implement ALL of 6.c > before too long, that it would catch up, and otherwise the intent is that > Rakudo would be leading on things that eventually become 6.d etc later. > > The original question would be more accurately phrased, "Any idea when > Rakudo will release implementing the full Perl 6.c?" > > -- Darren Duncan > > On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote: >> >> If that is the question, the answer is: the junction of “never" and “now". >> Which would also be the answer for Pumpking Perl 5, or any other programming >> language like ever. Because as long as people are using it, a programming >> language will evolve. Much like any human endeavour I would say. >> >>> On 25 Jul 2017,
Re: Announce: Rakudo Star Release 2017.07
On 2017-07-25 10:05 AM, Brandon Allbery wrote: On Tue, Jul 25, 2017 at 11:45 AM, Darren Duncan wrote: However I assume it is the 3 bullet points that the release announcement highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11. The fact the announcement highlights these implies they are part of the creators' definition of "complete". The "advanced macros" part, at least, probably needs to go away: a large part of the problem is that nobody actually knows what "advanced macros" for Perl 6 should do, or even look like. (See for example masak's 007, which is a playground for macros to try to get a handle on the question of what they ought to be/do.) I agree with your point and should further say that I think at this point the Rakudo announcements should stop naming that features are missing except where they are key show-stopper-for-some features. Don't highlight the fact that some things are missing. That would always be the case. At this point things are complete enough that most people wouldn't even notice things were missing if they weren't told and it doesn't affect them. In my opinion, non-blocking I/O is the only thing on the list that deserves to be highlighted, that and the warnings about the level of JVM support. -- Darren Duncan
Re: Announce: Rakudo Star Release 2017.07
On Tue, Jul 25, 2017 at 11:45 AM, Darren Duncan <dar...@darrenduncan.net> wrote: > However I assume it is the 3 bullet points that the release announcement > highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11. > The fact the announcement highlights these implies they are part of the > creators' definition of "complete". The "advanced macros" part, at least, probably needs to go away: a large part of the problem is that nobody actually knows what "advanced macros" for Perl 6 should do, or even look like. (See for example masak's 007, which is a playground for macros to try to get a handle on the question of what they ought to be/do.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
Re: Announce: Rakudo Star Release 2017.07
On 2017-07-25 8:32 AM, Steve Mynott wrote: On 25 July 2017 at 16:23, Darren Duncan <dar...@darrenduncan.net> wrote: There's a key difference however. While programming languages continue to evolve, the expectation is that a production-complete Rakudo would always be a functional superset (or equal to) the Perl 6 language specification which is current at the time. The Perl 6 language specification is the test suite. So if the test suite passes then it's complete! Which is of course a tautology. So by that definition, "complete" is that the arbitrary subset of the spec that an implementation chooses to do passes the tests for those parts, and the rest of the tests skip rather than fail. So I think it is reasonable for Rakudo to actually implement ALL of 6.c before too long, that it would catch up, and otherwise the intent is that Rakudo would be leading on things that eventually become 6.d etc later. Which missing parts are you concerned about? I'm not personally concerned about any parts at this time. It is ToddAndMargo that is concerned about it, who asked the question. However I assume it is the 3 bullet points that the release announcement highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11. The fact the announcement highlights these implies they are part of the creators' definition of "complete". -- Darren Duncan
Re: Announce: Rakudo Star Release 2017.07
On 25 July 2017 at 16:33, Stephen Wilcoxon <wilco...@gmail.com> wrote: > I don't see anything in the notes (though I may have missed it) about JVM. > I thought the plan was to get JVM functional again (though likely still > lagging MoarVM feature support) with the 2017.07 release? There are comments in the README "Please note that this release of Rakudo Star is *not* fully functional with the JVM backend from the Rakudo compiler. Use the JVM backend only if you are trying to help with fixing JVM support (which is best done upstream with the monthly Rakudo release). This is a known issue and it's not worth reporting JVM failures as bugs unless you have patches." The last time I tried it (and this was a while ago) I was able to build with JVM and run simple (dozen line) programs OK. But complex programs like zef didn't work and so installing modules wasn't possible. S
Re: Announce: Rakudo Star Release 2017.07
I don't see anything in the notes (though I may have missed it) about JVM. I thought the plan was to get JVM functional again (though likely still lagging MoarVM feature support) with the 2017.07 release? Perl 6 on MoarVM is definitely interesting but, to me at least, the single biggest practical impact or Rakudo was that it is (or was) supposed to run on JVM (allowing usage of any other libs on JVM and, probably more importantly, making it easier to convince management to allow using it). On Tue, Jul 25, 2017 at 10:23 AM, Darren Duncan <dar...@darrenduncan.net> wrote: > There's a key difference however. > > While programming languages continue to evolve, the expectation is that a > production-complete Rakudo would always be a functional superset (or equal > to) the Perl 6 language specification which is current at the time. > > So I think it is reasonable for Rakudo to actually implement ALL of 6.c > before too long, that it would catch up, and otherwise the intent is that > Rakudo would be leading on things that eventually become 6.d etc later. > > The original question would be more accurately phrased, "Any idea when > Rakudo will release implementing the full Perl 6.c?" > > -- Darren Duncan > > On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote: > >> If that is the question, the answer is: the junction of “never" and >> “now". Which would also be the answer for Pumpking Perl 5, or any other >> programming language like ever. Because as long as people are using it, a >> programming language will evolve. Much like any human endeavour I would >> say. >> >> On 25 Jul 2017, at 09:42, Andrew Kirkpatrick <uberm...@gmail.com> wrote: >>> >>> I assume the meaning is, roughly when is the implementation expected >>> to cover the entire spec? >>> >>> Answering this is probably an exercise in futility, because its up to >>> the community and not anyone in particular. >>> >>> On 25 July 2017 at 17:00, Elizabeth Mattijsen <l...@dijkmat.nl> wrote: >>> >> [snip] > > >>>>> >>>>> Any idea when the full Rakudo will be released? >>>>> >>>> >>>> What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo >>>> compiler release with a set of useful modules added (“batteries included”). >>>> >>>> So you could argue that Rakudo doesn’t get fuller than with Rakudo Star! >>>> >>> >>
Re: Announce: Rakudo Star Release 2017.07
On 25 July 2017 at 16:23, Darren Duncan <dar...@darrenduncan.net> wrote: > There's a key difference however. > > While programming languages continue to evolve, the expectation is that a > production-complete Rakudo would always be a functional superset (or equal > to) the Perl 6 language specification which is current at the time. The Perl 6 language specification is the test suite. So if the test suite passes then it's complete! Which is of course a tautology. > So I think it is reasonable for Rakudo to actually implement ALL of 6.c > before too long, that it would catch up, and otherwise the intent is that > Rakudo would be leading on things that eventually become 6.d etc later. Which missing parts are you concerned about? > The original question would be more accurately phrased, "Any idea when > Rakudo will release implementing the full Perl 6.c?" It's a volunteer effort so this happens whenever someone who cares enough about missing parts and who has the time and skills to implement does it. S
Re: Announce: Rakudo Star Release 2017.07
There's a key difference however. While programming languages continue to evolve, the expectation is that a production-complete Rakudo would always be a functional superset (or equal to) the Perl 6 language specification which is current at the time. So I think it is reasonable for Rakudo to actually implement ALL of 6.c before too long, that it would catch up, and otherwise the intent is that Rakudo would be leading on things that eventually become 6.d etc later. The original question would be more accurately phrased, "Any idea when Rakudo will release implementing the full Perl 6.c?" -- Darren Duncan On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote: If that is the question, the answer is: the junction of “never" and “now". Which would also be the answer for Pumpking Perl 5, or any other programming language like ever. Because as long as people are using it, a programming language will evolve. Much like any human endeavour I would say. On 25 Jul 2017, at 09:42, Andrew Kirkpatrick <uberm...@gmail.com> wrote: I assume the meaning is, roughly when is the implementation expected to cover the entire spec? Answering this is probably an exercise in futility, because its up to the community and not anyone in particular. On 25 July 2017 at 17:00, Elizabeth Mattijsen <l...@dijkmat.nl> wrote: [snip] Any idea when the full Rakudo will be released? What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler release with a set of useful modules added (“batteries included”). So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!
Re: Announce: Rakudo Star Release 2017.07
Were there any failures before the "Building NQP ..." step? Somehow the moarvm that's packaged with the rakudo star didn't end up getting installed into your .local/bin, so you're getting the previous version, which - unsurprisingly - isn't new enough for current NQP and Rakudo.
Re: Announce: Rakudo Star Release 2017.07
Attempted build on Arch Linux: perl Configure.pl --prefix=$HOME/.local --backend=moar --gen-moar --gen-moar Resulting in: Building NQP ... /usr/bin/perl Configure.pl --prefix=/home/mcarter/.local --backends=moar --make-install Creating tools/build/install-jvm-runner.pl ... ===SORRY!=== Found /home/mcarter/.local/bin/moar version 2017.04-53-g66c6dda, which is too old. Wanted at least 2017.07 No suitable MoarVM (moar executable) found using the --prefix (You can get a MoarVM built automatically with --gen-moar.) Command failed (status 65280): /usr/bin/perl Configure.pl --prefix=/home/mcarter/.local --backends=moar --make-install
Re: Announce: Rakudo Star Release 2017.07
If that is the question, the answer is: the junction of “never" and “now".
Which would also be the answer for Pumpking Perl 5, or any other programming
language like ever. Because as long as people are using it, a programming
language will evolve. Much like any human endeavour I would say.
> On 25 Jul 2017, at 09:42, Andrew Kirkpatrick <uberm...@gmail.com> wrote:
>
> I assume the meaning is, roughly when is the implementation expected
> to cover the entire spec?
>
> Answering this is probably an exercise in futility, because its up to
> the community and not anyone in particular.
>
> On 25 July 2017 at 17:00, Elizabeth Mattijsen <l...@dijkmat.nl> wrote:
>>> On 25 Jul 2017, at 05:57, ToddAndMargo <toddandma...@zoho.com> wrote:
>>> On 07/24/2017 11:40 AM, Steve Mynott wrote:
>>>> A useful and usable production distribution of Perl 6
>>>> On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
>>>> announce the July 2017 release of "Rakudo Star", a useful and usable
>>>> production distribution of Perl 6. The tarball for the July 2017
>>>> release is available from https://rakudo.perl6.org/downloads/star/.
>>>> Binaries for macOS and Windows (64 bit) are also available.
>>>> This is the eighth post-Christmas (production) release of Rakudo Star
>>>> and implements Perl v6.c. It comes with support for the MoarVM backend
>>>> (all module tests pass on supported platforms).
>>>> IMPORTANT: "panda" is to be removed very shortly since it is
>>>> deprecated. Please use "zef" instead.
>>>> Currently, Star is on a quarterly release cycle and 2017.10 (October)
>>>> will follow later this year.
>>>> Please note that this release of Rakudo Star is not fully functional
>>>> with the JVM backend from the Rakudo compiler. Please use the MoarVM
>>>> backend only.
>>>> In the Perl 6 world, we make a distinction between the language ("Perl
>>>> 6") and specific implementations of the language such as "Rakudo
>>>> Perl".
>>>> This Star release includes release 2017.07 of the Rakudo Perl 6
>>>> compiler, version 2017.07 MoarVM, plus various modules, documentation,
>>>> and other resources collected from the Perl 6 community.
>>>> Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
>>>> than the release NQP 2017.07 in order to fix the --ll-exception
>>>> command line flag.
>>>> The Rakudo compiler changes since the last Rakudo Star release of
>>>> 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
>>>> under the "rakudo/docs/announce" directory of the source distribution.
>>>> Notable changes in modules shipped with Rakudo Star:
>>>> + DBIish: Doc and CI updates
>>>> + doc: Too many to list. p6doc fixed.
>>>> + grammar-debugger: Works again now.
>>>> + p6-io-string: New dep for doc.
>>>> + p6-native-resources: Removed since deprecated and not used by linenoise.
>>>> + panda: Officially deprecate panda in favour of zef.
>>>> + perl6-Test-When: New dep for perl6-pod-to-bigpage.
>>>> + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
>>>> + tap-harness6: Replaces deprecated tap-harness6-prove6.
>>>> + zef: Too many to list.
>>>> There are some key features of Perl 6 that Rakudo Star does not yet
>>>> handle appropriately, although they will appear in upcoming releases.
>>>> Some of the not-quite-there features include:
>>>> + advanced macros
>>>> + non-blocking I/O (in progress)
>>>> + some bits of Synopsis 9 and 11
>>>> There is an online resource at http://perl6.org/compilers/features
>>>> that lists the known implemented and missing features of Rakudo's
>>>> backends and other Perl 6 implementations.
>>>> In many places we've tried to make Rakudo smart enough to inform the
>>>> programmer that a given feature isn't implemented, but there are many
>>>> that we've missed. Bug reports about missing and broken features are
>>>> welcomed at rakudo...@perl.org.
>>>> See https://perl6.org/ for links to much more information about Perl
>>>> 6, including documentation, example code, tutorials, presentations,
>>>> reference materials, design documents, and other supporting resources.
>>>> Some Perl 6 tutorials are available under the "docs" directory in the
>>>> release tarball.
>>>> The development team thanks all of the contributors and sponsors for
>>>> making Rakudo Star possible. If you would like to contribute, see
>>>> http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
>>>> mailing list, or join us on IRC #perl6 on freenode.
>>>
>>>
>>> Any idea when the full Rakudo will be released?
>>
>> What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler
>> release with a set of useful modules added (“batteries included”).
>>
>> So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!
Re: Announce: Rakudo Star Release 2017.07
I assume the meaning is, roughly when is the implementation expected
to cover the entire spec?
Answering this is probably an exercise in futility, because its up to
the community and not anyone in particular.
On 25 July 2017 at 17:00, Elizabeth Mattijsen <l...@dijkmat.nl> wrote:
>> On 25 Jul 2017, at 05:57, ToddAndMargo <toddandma...@zoho.com> wrote:
>> On 07/24/2017 11:40 AM, Steve Mynott wrote:
>>> A useful and usable production distribution of Perl 6
>>> On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
>>> announce the July 2017 release of "Rakudo Star", a useful and usable
>>> production distribution of Perl 6. The tarball for the July 2017
>>> release is available from https://rakudo.perl6.org/downloads/star/.
>>> Binaries for macOS and Windows (64 bit) are also available.
>>> This is the eighth post-Christmas (production) release of Rakudo Star
>>> and implements Perl v6.c. It comes with support for the MoarVM backend
>>> (all module tests pass on supported platforms).
>>> IMPORTANT: "panda" is to be removed very shortly since it is
>>> deprecated. Please use "zef" instead.
>>> Currently, Star is on a quarterly release cycle and 2017.10 (October)
>>> will follow later this year.
>>> Please note that this release of Rakudo Star is not fully functional
>>> with the JVM backend from the Rakudo compiler. Please use the MoarVM
>>> backend only.
>>> In the Perl 6 world, we make a distinction between the language ("Perl
>>> 6") and specific implementations of the language such as "Rakudo
>>> Perl".
>>> This Star release includes release 2017.07 of the Rakudo Perl 6
>>> compiler, version 2017.07 MoarVM, plus various modules, documentation,
>>> and other resources collected from the Perl 6 community.
>>> Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
>>> than the release NQP 2017.07 in order to fix the --ll-exception
>>> command line flag.
>>> The Rakudo compiler changes since the last Rakudo Star release of
>>> 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
>>> under the "rakudo/docs/announce" directory of the source distribution.
>>> Notable changes in modules shipped with Rakudo Star:
>>> + DBIish: Doc and CI updates
>>> + doc: Too many to list. p6doc fixed.
>>> + grammar-debugger: Works again now.
>>> + p6-io-string: New dep for doc.
>>> + p6-native-resources: Removed since deprecated and not used by linenoise.
>>> + panda: Officially deprecate panda in favour of zef.
>>> + perl6-Test-When: New dep for perl6-pod-to-bigpage.
>>> + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
>>> + tap-harness6: Replaces deprecated tap-harness6-prove6.
>>> + zef: Too many to list.
>>> There are some key features of Perl 6 that Rakudo Star does not yet
>>> handle appropriately, although they will appear in upcoming releases.
>>> Some of the not-quite-there features include:
>>> + advanced macros
>>> + non-blocking I/O (in progress)
>>> + some bits of Synopsis 9 and 11
>>> There is an online resource at http://perl6.org/compilers/features
>>> that lists the known implemented and missing features of Rakudo's
>>> backends and other Perl 6 implementations.
>>> In many places we've tried to make Rakudo smart enough to inform the
>>> programmer that a given feature isn't implemented, but there are many
>>> that we've missed. Bug reports about missing and broken features are
>>> welcomed at rakudo...@perl.org.
>>> See https://perl6.org/ for links to much more information about Perl
>>> 6, including documentation, example code, tutorials, presentations,
>>> reference materials, design documents, and other supporting resources.
>>> Some Perl 6 tutorials are available under the "docs" directory in the
>>> release tarball.
>>> The development team thanks all of the contributors and sponsors for
>>> making Rakudo Star possible. If you would like to contribute, see
>>> http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
>>> mailing list, or join us on IRC #perl6 on freenode.
>>
>>
>> Any idea when the full Rakudo will be released?
>
> What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler
> release with a set of useful modules added (“batteries included”).
>
> So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!
Re: Announce: Rakudo Star Release 2017.07
> On 25 Jul 2017, at 05:57, ToddAndMargo <toddandma...@zoho.com> wrote:
> On 07/24/2017 11:40 AM, Steve Mynott wrote:
>> A useful and usable production distribution of Perl 6
>> On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
>> announce the July 2017 release of "Rakudo Star", a useful and usable
>> production distribution of Perl 6. The tarball for the July 2017
>> release is available from https://rakudo.perl6.org/downloads/star/.
>> Binaries for macOS and Windows (64 bit) are also available.
>> This is the eighth post-Christmas (production) release of Rakudo Star
>> and implements Perl v6.c. It comes with support for the MoarVM backend
>> (all module tests pass on supported platforms).
>> IMPORTANT: "panda" is to be removed very shortly since it is
>> deprecated. Please use "zef" instead.
>> Currently, Star is on a quarterly release cycle and 2017.10 (October)
>> will follow later this year.
>> Please note that this release of Rakudo Star is not fully functional
>> with the JVM backend from the Rakudo compiler. Please use the MoarVM
>> backend only.
>> In the Perl 6 world, we make a distinction between the language ("Perl
>> 6") and specific implementations of the language such as "Rakudo
>> Perl".
>> This Star release includes release 2017.07 of the Rakudo Perl 6
>> compiler, version 2017.07 MoarVM, plus various modules, documentation,
>> and other resources collected from the Perl 6 community.
>> Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
>> than the release NQP 2017.07 in order to fix the --ll-exception
>> command line flag.
>> The Rakudo compiler changes since the last Rakudo Star release of
>> 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
>> under the "rakudo/docs/announce" directory of the source distribution.
>> Notable changes in modules shipped with Rakudo Star:
>> + DBIish: Doc and CI updates
>> + doc: Too many to list. p6doc fixed.
>> + grammar-debugger: Works again now.
>> + p6-io-string: New dep for doc.
>> + p6-native-resources: Removed since deprecated and not used by linenoise.
>> + panda: Officially deprecate panda in favour of zef.
>> + perl6-Test-When: New dep for perl6-pod-to-bigpage.
>> + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
>> + tap-harness6: Replaces deprecated tap-harness6-prove6.
>> + zef: Too many to list.
>> There are some key features of Perl 6 that Rakudo Star does not yet
>> handle appropriately, although they will appear in upcoming releases.
>> Some of the not-quite-there features include:
>> + advanced macros
>> + non-blocking I/O (in progress)
>> + some bits of Synopsis 9 and 11
>> There is an online resource at http://perl6.org/compilers/features
>> that lists the known implemented and missing features of Rakudo's
>> backends and other Perl 6 implementations.
>> In many places we've tried to make Rakudo smart enough to inform the
>> programmer that a given feature isn't implemented, but there are many
>> that we've missed. Bug reports about missing and broken features are
>> welcomed at rakudo...@perl.org.
>> See https://perl6.org/ for links to much more information about Perl
>> 6, including documentation, example code, tutorials, presentations,
>> reference materials, design documents, and other supporting resources.
>> Some Perl 6 tutorials are available under the "docs" directory in the
>> release tarball.
>> The development team thanks all of the contributors and sponsors for
>> making Rakudo Star possible. If you would like to contribute, see
>> http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
>> mailing list, or join us on IRC #perl6 on freenode.
>
>
> Any idea when the full Rakudo will be released?
What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler
release with a set of useful modules added (“batteries included”).
So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!
Re: Announce: Rakudo Star Release 2017.07
On 07/24/2017 11:40 AM, Steve Mynott wrote:
A useful and usable production distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the July 2017 release of "Rakudo Star", a useful and usable
production distribution of Perl 6. The tarball for the July 2017
release is available from https://rakudo.perl6.org/downloads/star/.
Binaries for macOS and Windows (64 bit) are also available.
This is the eighth post-Christmas (production) release of Rakudo Star
and implements Perl v6.c. It comes with support for the MoarVM backend
(all module tests pass on supported platforms).
IMPORTANT: "panda" is to be removed very shortly since it is
deprecated. Please use "zef" instead.
Currently, Star is on a quarterly release cycle and 2017.10 (October)
will follow later this year.
Please note that this release of Rakudo Star is not fully functional
with the JVM backend from the Rakudo compiler. Please use the MoarVM
backend only.
In the Perl 6 world, we make a distinction between the language ("Perl
6") and specific implementations of the language such as "Rakudo
Perl".
This Star release includes release 2017.07 of the Rakudo Perl 6
compiler, version 2017.07 MoarVM, plus various modules, documentation,
and other resources collected from the Perl 6 community.
Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
than the release NQP 2017.07 in order to fix the --ll-exception
command line flag.
The Rakudo compiler changes since the last Rakudo Star release of
2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
under the "rakudo/docs/announce" directory of the source distribution.
Notable changes in modules shipped with Rakudo Star:
+ DBIish: Doc and CI updates
+ doc: Too many to list. p6doc fixed.
+ grammar-debugger: Works again now.
+ p6-io-string: New dep for doc.
+ p6-native-resources: Removed since deprecated and not used by linenoise.
+ panda: Officially deprecate panda in favour of zef.
+ perl6-Test-When: New dep for perl6-pod-to-bigpage.
+ perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
+ tap-harness6: Replaces deprecated tap-harness6-prove6.
+ zef: Too many to list.
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
+ advanced macros
+ non-blocking I/O (in progress)
+ some bits of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See https://perl6.org/ for links to much more information about Perl
6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in the
release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC #perl6 on freenode.
Any idea when the full Rakudo will be released?
Announce: Rakudo Star Release 2017.07
A useful and usable production distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the July 2017 release of "Rakudo Star", a useful and usable
production distribution of Perl 6. The tarball for the July 2017
release is available from https://rakudo.perl6.org/downloads/star/.
Binaries for macOS and Windows (64 bit) are also available.
This is the eighth post-Christmas (production) release of Rakudo Star
and implements Perl v6.c. It comes with support for the MoarVM backend
(all module tests pass on supported platforms).
IMPORTANT: "panda" is to be removed very shortly since it is
deprecated. Please use "zef" instead.
Currently, Star is on a quarterly release cycle and 2017.10 (October)
will follow later this year.
Please note that this release of Rakudo Star is not fully functional
with the JVM backend from the Rakudo compiler. Please use the MoarVM
backend only.
In the Perl 6 world, we make a distinction between the language ("Perl
6") and specific implementations of the language such as "Rakudo
Perl".
This Star release includes release 2017.07 of the Rakudo Perl 6
compiler, version 2017.07 MoarVM, plus various modules, documentation,
and other resources collected from the Perl 6 community.
Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
than the release NQP 2017.07 in order to fix the --ll-exception
command line flag.
The Rakudo compiler changes since the last Rakudo Star release of
2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
under the "rakudo/docs/announce" directory of the source distribution.
Notable changes in modules shipped with Rakudo Star:
+ DBIish: Doc and CI updates
+ doc: Too many to list. p6doc fixed.
+ grammar-debugger: Works again now.
+ p6-io-string: New dep for doc.
+ p6-native-resources: Removed since deprecated and not used by linenoise.
+ panda: Officially deprecate panda in favour of zef.
+ perl6-Test-When: New dep for perl6-pod-to-bigpage.
+ perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
+ tap-harness6: Replaces deprecated tap-harness6-prove6.
+ zef: Too many to list.
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
+ advanced macros
+ non-blocking I/O (in progress)
+ some bits of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See https://perl6.org/ for links to much more information about Perl
6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in the
release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC #perl6 on freenode.
--
4096R/EA75174B Steve Mynott <steve.myn...@gmail.com>
release names
Holiday || butterfly ? Why not holiday && butterfly ? Perl6 fuses so many other things. In any case, we would use the abbreviation D/E/F ... Adding a name is just being whimsical. So lets be doubly whimsical.
Announce: Rakudo Star Release 2017.04
A useful and usable production distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the April 2017 release of "Rakudo Star", a useful and usable
production distribution of Perl 6. The tarball for the April 2017
release is available from https://rakudo.perl6.org/downloads/star/.
Binaries for macOS and Windows (64 bit) are also available.
This is the seventh post-Christmas (production) release of Rakudo Star
and implements Perl v6.c. It comes with support for the MoarVM backend
(all module tests pass on supported platforms).
This release includes "zef" as module installer. "panda" is to be
shortly replaced by "zef" and will be removed in the near future.
It's hoped to produce quarterly Rakudo Star releases during 2017 with
2017.07 (July) and 2017.10 (October) to follow.
Please note that this release of Rakudo Star is not fully functional
with the JVM backend from the Rakudo compiler. Please use the MoarVM
backend only.
In the Perl 6 world, we make a distinction between the language ("Perl
6") and specific implementations of the language such as "Rakudo
Perl".
This Star release includes [release 2017.04.3] of the Rakudo Perl 6
compiler, version 2017.04-53-g66c6dda of MoarVM, plus various modules,
documentation, and other resources collected from the Perl 6
community.
The Rakudo compiler changes since the last Rakudo Star release of
2017.01 are now listed in "2017.02.md" and "2017.04.md" under the
"rakudo/docs/announce" directory of the source distribution.
In particular This release featured many important improvements to the
IO subsystem thanks to Zoffix and the support of the Perl Foundation.
Please see Part 1: http://rakudo.org/2017/04/02/upgrade Part 2:
http://rakudo.org/2017/04/03/part-2 Part 3:
http://rakudo.org/2017/04/17/final-notes
Note there were point releases of 2017.04 so also see "2017.04.1.md",
"2017.04.2.md" and "2017.04.3.md".
Notable changes in modules shipped with Rakudo Star:
+ DBIish: New version with pg-consume-input
+ doc: Too many to list. Large number of "IO Grant" doc changes.
+ json\_fast: Too many to list. Big performance improvements.
+ perl6-lwp-simple: Fix for lexical require and incorrect regex for
absolute URL matcher
+ test-mock: Enable concurrent use of mock objects
+ uri: Encoding fixes
+ zef: Too many to list. IO fixage.
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
advanced macros
non-blocking I/O (in progress)
some bits of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See https://perl6.org/ for links to much more information about Perl
6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in the
release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC #perl6 on freenode.
--
4096R/EA75174B Steve Mynott <steve.myn...@gmail.com>
Announce: Rakudo Star Release 2017.01
A useful and usable production distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the November 2016 release of "Rakudo Star", a useful and usable
production distribution of Perl 6. The tarball for the January 2017 release
is available from <http://rakudo.org/downloads/star/>.
Binaries for macOS and Windows (64 bit) are also available.
This is the sixth post-Christmas (production) release of Rakudo Star and
implements Perl v6.c. It comes with support for the MoarVM backend (all module
tests pass on supported platforms).
This is the first Rakudo Star release to include "zef" as module installer.
"panda" is to be shortly replaced by "zef" and will be removed in the near
future.
It's hoped to produce quarterly Rakudo Star releases during 2017 with 2017.04
(April), 2017.07 (July) and 2017.10 (October) to follow.
Please note that this release of Rakudo Star is not fully functional with the
JVM backend from the Rakudo compiler. Please use the MoarVM backend only.
In the Perl 6 world, we make a distinction between the language ("Perl 6") and
specific implementations of the language such as "Rakudo Perl".
This Star release includes [release 2017.01] of the [Rakudo Perl 6 compiler],
version 2017.01 of [MoarVM], plus various modules, documentation, and other
resources collected from the Perl 6 community.
The Rakudo compiler changes since the last Rakudo Star release of 2016.11 are
now listed in "2016.12.md" and "2017.01.md" under the "rakudo/docs/announce"
directory of the source distribution.
Notable changes in modules shipped with Rakudo Star:
+ DBIish: Pg: TypeConverter post-merge cleanup
+ Linenoise: Remove dependency on Native::Resources
+ Pod-To-HTML: Bump version for #22 fix
+ Terminal-ANSIColor: Drop 'nqp' dependency
+ doc: Too many to list
+ json: Fix parsing of string literals with a leading combining character.
+ json\_fast: bump version since we now escape null bytes
+ panda: modified to warn of its removal in the short term
+ perl6-http-easy: Several pull requests merged
+ perl6-lwp-simple: Tweak tests to work with TAP::Harness
+ perl6-pod-to-bigpage: bump version
+ test-mock: Bump version.
+ zef: imported
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* non-blocking I/O (in progress)
* some bits of Synopsis 9 and 11
There is an online resource at <http://perl6.org/compilers/features>
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at <rakudo...@perl.org>.
See <http://perl6.org/> for links to much more information about
Perl 6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
<http://rakudo.org/how-to-help>, ask on the <perl6-compi...@perl.org>
mailing list, or join us on IRC #perl6 on freenode.
--
4096R/EA75174B Steve Mynott <steve.myn...@gmail.com>
Re: Announce: Rakudo Star Release 2016.07
That is quite a step forward! Happy 22nd, All! On Jul 22, 2016 4:01 AM, "Steve Mynott" <steve.myn...@gmail.com> wrote: > > On behalf of the Rakudo and Perl 6 development teams, I’m pleased to > announce the July 2016 release of “Rakudo Star”, a useful and usable > production distribution of Perl 6. The tarball for the July 2016 release is > available from http://rakudo.org/downloads/star/. > > This is the third post-Christmas (production) release of Rakudo Star and > implements Perl v6.c. It comes with support for the MoarVM backend (all > module tests pass on supported platforms). > > Please note that this release of Rakudo Star is not fully functional with > the JVM backend from the Rakudo compiler. Please use the MoarVM backend > only. > > In the Perl 6 world, we make a distinction between the language (“Perl 6″) > and specific implementations of the language such as “Rakudo Perl”. This > Star release includes release 2016.07 of the Rakudo Perl 6 compiler, > version 2016.07 of MoarVM, plus various modules, documentation, and other > resources collected from the Perl 6 community. > > Some of the new compiler features since the last Rakudo Star release > include: > > + Ability to use a customer debugger module > + The “is-approx” sub from Test.pm6 now allows for relative/absolute > tolerance > + A fail in a custom BUILD will now be returned, rather than thrown > + Introduce .Map coercer > + Implement alternate ways to call subtest > + Support for new leap-second at the end of 2016 > + The “is required” trait on Attributes can now take a Bool or a Str > + IO::[Path,Handle] gained a .mode method which returns the POSIX file > permissions > + Distribution is now a role interface that enables encapsulating IO used > for distribution installation > + CompUnit::Repository::Installation now uses the new Distribution > interface > + Custom repository implementations now supported, including precompilation > > Compiler maintenance since the last Rakudo Star release includes: > > + Basic object creation (using either .new or .bless) now up to 3x faster > + All routines now have less overhead > + The MMD cache accepts candidates with named parameters if it can. (This > made adverbed slices about 18x as fast) > + Sigificant optimizations for speed in many parts of the system (.map, > gather/take etc.) > + Many precompilation fixes (including EVAL and improved support of OS > packaging) > + Arrays with holes (e.g. from :delete) now correctly iterate/auto-vivify > + An issue with reverse dependencies of installed modules was fixed > + “is_approx” sub (note underscore) from Test.pm6 deprecated > + Harden Mu.Str against moving GC > + Simplify $USER/$GROUP initialization > + Mu can now be the result of a Promise > + samewith() now also works on non-multi’s > + Many fixes in the area of pre-compilation and installing modules > + count-only and bool-only now are optional methods in Iterators (only to > be implemented if they can work without generating anything) > + IO::ArgFiles.slurp / IO::ArgFiles.eof are fixed > + REPL whitespace and error handling > + CompUnit::Repository::Installation no longer considers bin/xxx and > resources/bin/xxx the same content address > + min/max on Failures throw instead of returning ±Inf > + NativeCall’s is mangled trait no longer ignored for CPPStruct > + Many Str, List and Array methods much faster > + Map/Hash initializations are now 30% faster > + make DESTDIR now correctly finds CompUnit::Repository::Staging > + Output from Test.pm6′s diag() is no longer lost in non-verbose prove > output when called at the start of the test file or during TODO tests > + Improved error messages > > Notable changes in modules shipped with Rakudo Star: > > + DBIish: v0.5.9 (with many Oracle/MySQL fixes) plus README.pod and > mojibake fixes > + NativeHelpers-Blob: v0.1.10 > + PSGI: v1.2.0 supports P6SGI 0.7Draft > + Pod-To-HTML: v0.1.2 plus fixes > + debugger-ui-commandline: README fixes > + doc: many fixes to documentation content and HTML generation > + panda: Avoid Rakudo internals deprecation warning and don’t require > Build.pm to inherit Panda::Builder > + perl6-file-which: CI fixes > + perl6-http-easy: v1.1.0 (with more flexible P6SGI support) plus avoid > errors in binary request > + shell-command: Mention already implemented commands missing from README > + perl6-lwp-simple: track github.com/perl6/perl6-lwp-simple as upstream > (as panda does) which has a test fix needed since we don’t support https in > R* and a test url had a new https redirect > > perl6intro.pdf has also been updated. > > There are some key features of Perl 6 that Rakudo Star does not yet handle > appropriately, although they
Announce: Rakudo Star Release 2016.07
On behalf of the Rakudo and Perl 6 development teams, I’m pleased to announce the July 2016 release of “Rakudo Star”, a useful and usable production distribution of Perl 6. The tarball for the July 2016 release is available from http://rakudo.org/downloads/star/. This is the third post-Christmas (production) release of Rakudo Star and implements Perl v6.c. It comes with support for the MoarVM backend (all module tests pass on supported platforms). Please note that this release of Rakudo Star is not fully functional with the JVM backend from the Rakudo compiler. Please use the MoarVM backend only. In the Perl 6 world, we make a distinction between the language (“Perl 6″) and specific implementations of the language such as “Rakudo Perl”. This Star release includes release 2016.07 of the Rakudo Perl 6 compiler, version 2016.07 of MoarVM, plus various modules, documentation, and other resources collected from the Perl 6 community. Some of the new compiler features since the last Rakudo Star release include: + Ability to use a customer debugger module + The “is-approx” sub from Test.pm6 now allows for relative/absolute tolerance + A fail in a custom BUILD will now be returned, rather than thrown + Introduce .Map coercer + Implement alternate ways to call subtest + Support for new leap-second at the end of 2016 + The “is required” trait on Attributes can now take a Bool or a Str + IO::[Path,Handle] gained a .mode method which returns the POSIX file permissions + Distribution is now a role interface that enables encapsulating IO used for distribution installation + CompUnit::Repository::Installation now uses the new Distribution interface + Custom repository implementations now supported, including precompilation Compiler maintenance since the last Rakudo Star release includes: + Basic object creation (using either .new or .bless) now up to 3x faster + All routines now have less overhead + The MMD cache accepts candidates with named parameters if it can. (This made adverbed slices about 18x as fast) + Sigificant optimizations for speed in many parts of the system (.map, gather/take etc.) + Many precompilation fixes (including EVAL and improved support of OS packaging) + Arrays with holes (e.g. from :delete) now correctly iterate/auto-vivify + An issue with reverse dependencies of installed modules was fixed + “is_approx” sub (note underscore) from Test.pm6 deprecated + Harden Mu.Str against moving GC + Simplify $USER/$GROUP initialization + Mu can now be the result of a Promise + samewith() now also works on non-multi’s + Many fixes in the area of pre-compilation and installing modules + count-only and bool-only now are optional methods in Iterators (only to be implemented if they can work without generating anything) + IO::ArgFiles.slurp / IO::ArgFiles.eof are fixed + REPL whitespace and error handling + CompUnit::Repository::Installation no longer considers bin/xxx and resources/bin/xxx the same content address + min/max on Failures throw instead of returning ±Inf + NativeCall’s is mangled trait no longer ignored for CPPStruct + Many Str, List and Array methods much faster + Map/Hash initializations are now 30% faster + make DESTDIR now correctly finds CompUnit::Repository::Staging + Output from Test.pm6′s diag() is no longer lost in non-verbose prove output when called at the start of the test file or during TODO tests + Improved error messages Notable changes in modules shipped with Rakudo Star: + DBIish: v0.5.9 (with many Oracle/MySQL fixes) plus README.pod and mojibake fixes + NativeHelpers-Blob: v0.1.10 + PSGI: v1.2.0 supports P6SGI 0.7Draft + Pod-To-HTML: v0.1.2 plus fixes + debugger-ui-commandline: README fixes + doc: many fixes to documentation content and HTML generation + panda: Avoid Rakudo internals deprecation warning and don’t require Build.pm to inherit Panda::Builder + perl6-file-which: CI fixes + perl6-http-easy: v1.1.0 (with more flexible P6SGI support) plus avoid errors in binary request + shell-command: Mention already implemented commands missing from README + perl6-lwp-simple: track github.com/perl6/perl6-lwp-simple as upstream (as panda does) which has a test fix needed since we don’t support https in R* and a test url had a new https redirect perl6intro.pdf has also been updated. There are some key features of Perl 6 that Rakudo Star does not yet handle appropriately, although they will appear in upcoming releases. Some of the not-quite-there features include: + advanced macros + non-blocking I/O (in progress) + some bits of Synopsis 9 and 11 + There is an online resource at http://perl6.org/compilers/features that lists the known implemented and missing features of Rakudo’s backends and other Perl 6 implementations. In many places we’ve tried to make Rakudo smart enough to inform the programmer that a given feature isn’t implemented, but there are many that we’ve missed. Bug reports about missing and broken features are welcomed at rakudo...@perl.org. See http://perl6
Announce: Mac OS X Installer for release 2016.01
Thanks to Steve Mynott a Mac OS X installer is now available. This installer has the ".dmg" file extension and is available from http://rakudo.org/downloads/star/.
Re: Needed: Rakudo Star with 6.c Christmas Perl 6 release
FYI, http://blogs.perl.org/users/coke/2016/01/perl-6c-christmas-rakudo-star-coming-soon.html We hope to have an R* release out in the next two weeks. Thanks for your patience. On Sat, Jan 16, 2016 at 1:45 PM, Brandon Allbery <allber...@gmail.com> wrote: > On Sat, Jan 16, 2016 at 1:40 PM, James E Keenan <jk...@verizon.net> wrote: >> >> Is there a timeline for the release of a Rakudo Star with 6.c? > > > I don't think there is a specific timeline, but given the rakudo bug fixes > since 6.c (in particular with CompUnitRepo, which would have made it > difficult to install the modules one expects in Star) it was correct to > delay a Star release. Hopefully it'll happen in the next few days. > > -- > brandon s allbery kf8nh sine nomine associates > allber...@gmail.com ballb...@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net -- Will "Coke" Coleda
Re: Needed: Rakudo Star with 6.c Christmas Perl 6 release
On 01/25/2016 08:49 AM, Will Coleda wrote: FYI, http://blogs.perl.org/users/coke/2016/01/perl-6c-christmas-rakudo-star-coming-soon.html We hope to have an R* release out in the next two weeks. Thanks for your patience. Thanks for the update! jimk
Re: Needed: Rakudo Star with 6.c Christmas Perl 6 release
On Sat, Jan 16, 2016 at 1:40 PM, James E Keenan <jk...@verizon.net> wrote: > Is there a timeline for the release of a Rakudo Star with 6.c? > I don't think there is a specific timeline, but given the rakudo bug fixes since 6.c (in particular with CompUnitRepo, which would have made it difficult to install the modules one expects in Star) it was correct to delay a Star release. Hopefully it'll happen in the next few days. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
Needed: Rakudo Star with 6.c Christmas Perl 6 release
Today, I posted on the ny.pm mailing list an announcement that I will attempt to organize a Perl 6 Beginners study group in New York City. I have been advised that for an introductory-level group, the Rakudo Star release would be the way to go. However, when I went here: http://rakudo.org/how-to-get-rakudo/ ... I read this: "NOTE: the Rakudo Star with 6.c Christmas Perl 6 release is not yet available. Check back soon or try one of the older versions." This is what, back in the day, we used to call a 'bummer'. We have people -- including non-Perl programmers -- excited about Perl 6 -- but we don't have the easy on-ramp. Is there a timeline for the release of a Rakudo Star with 6.c? Thank you very much. Jim Keenan
Re: release?
On Tue, Dec 29, 2015 at 11:39 AM, webmind <webm...@puscii.nl> wrote: > > Yes, wouldn't it make sense to couple the rakudo release version to the > language it implements? > Naw -- there'll be probably monthly rakudo releases but the Specification releases should be much less frequent -- like maybe every few months (at first) or yearly is my guess. This might be less confusing if: * We referred more often to rakudo instead of perl6 when we mean the implementation (you compile with gcc, not "c"; rakudo confusingly calls it's interpreter "perl6") * Get more implementations! If we had like 3-4 implementations to choose from then it might be more obvious what was going on. Probably there would be a stronger argument for the "perl6" binary to be either renamed to "rakudo" or to be a symlink to whatever your current-perl6-implementation is were there an alternative implementation ... but there isn't... so ... I guess someone should do that. :) ... though there actually ARE a few others, but none nearly as complete as Rakudo, afaik * https://github.com/sorear/niecza - CLR * http://fglock.github.io/Perlito/ - Perlito6 written mostly in Perl6 (lots of other interesting Perlito stuff) * http://perl6.org/compilers/features - comparison * several abandoned ones (e.g. Pugs) --Brock
Re: release?
That's how I have Perl 6 (and a number of other packages) set up; a version-agnostic name in a $PATH place, symbolically linking to package directory. On 12/31/15, Philip Hazelden <philip.hazel...@gmail.com> wrote: > Note that if we want scripts to be interpreter-agnostic, the perl6 binary > needs to exist for #! purposes. So renaming it would be bad, but a simlink > would work. > > On Thu, Dec 31, 2015 at 2:27 PM Brock Wilcox <awwa...@thelackthereof.org> > wrote: > >> On Tue, Dec 29, 2015 at 11:39 AM, webmind <webm...@puscii.nl> wrote: >> >>> >>> Yes, wouldn't it make sense to couple the rakudo release version to the >>> language it implements? >>> >> >> Naw -- there'll be probably monthly rakudo releases but the Specification >> releases should be much less frequent -- like maybe every few months (at >> first) or yearly is my guess. >> >> This might be less confusing if: >> * We referred more often to rakudo instead of perl6 when we mean the >> implementation (you compile with gcc, not "c"; rakudo confusingly calls >> it's interpreter "perl6") >> * Get more implementations! If we had like 3-4 implementations to choose >> from then it might be more obvious what was going on. >> >> Probably there would be a stronger argument for the "perl6" binary to be >> either renamed to "rakudo" or to be a symlink to whatever your >> current-perl6-implementation is were there an alternative implementation >> ... but there isn't... so ... I guess someone should do that. :) >> >> ... though there actually ARE a few others, but none nearly as complete >> as >> Rakudo, afaik >> >> * https://github.com/sorear/niecza - CLR >> * http://fglock.github.io/Perlito/ - Perlito6 written mostly in Perl6 >> (lots of other interesting Perlito stuff) >> * http://perl6.org/compilers/features - comparison >> * several abandoned ones (e.g. Pugs) >> >> --Brock >> >> >
Re: release?
On 29/12/15 17:13, andy_b...@wiwb.uscourts.gov wrote:
> On Tue, Dec 29, 2015 at 01:57:57AM -0800, Darren Duncan wrote:
>>> On that note, are there going to be Perl 6 versions 6.x.y where {x,y} are
>> > integers? Will 6.0.0 be the first such one? -- Darren Duncan
>
> On Tue, Dec 29, 2015 Patrick Michaud wrote:
>> "Perl 6" is a language, not an implementation of that language. Think
> of "Perl 6" as being like "C", "C++", "Javascript", etc., where the
> language is separate from the (many) implementations of that language.
>
> I'm just a very ordinary perl hacker here, but Alex's point I think
> should be addressed. Most of us (i.e ordinary, un-language
> implementation geeks) are looking to download a Perl6 and if it's rakudo
> x.y.z, fine, but make that seem like something like perl.6.tar.gz. It
> would seem that gently introducing the complete separation w/ a little
> of Perl's famous (to me) "syntatic sugar" (meta-syntatic?) to help us
> getting started. Maybe the lower case distinction, "perl6.x.y" vs "Perl
> 6.c", would soothe both sides of the discussion.
Yes, wouldn't it make sense to couple the rakudo release version to the
language it implements?
Thanks for all your replies.
--
GPG Key: https://u2m.nl/data/webmind.asc
GPG Fingerprint: 0506976E 234653B4 A628EC33 E23D16EE FCF154AE
XMPP webm...@puscii.nl: D79970A8 7EC43E29 186D86BA 590F20F6 4C7930B8
XMPP webm...@laglab.org: 11E91112 091881F7 53EF6108 63C48543 C74D035C
u2m.nl (exp: 08/04/2016) SHA256:
C2:40:67:22:25:52:29:AF:DF:50:4E:2A:6B:32:6D:BC:5B:1E:CA:7D:52:3B:4C:4A:21:5D:C8:E5:AE:7D:1A:09
Puscii (exp: 04/03/2016) SHA256:
F9:C7:B1:B7:90:6B:17:BF:84:93:93:7C:0F:B4:FD:BE:E3:C0:71:9D:83:01:ED:3A:96:FE:FC:82:9D:30:51:C9
0xFCF154AE.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
Re: release?
Note that if we want scripts to be interpreter-agnostic, the perl6 binary needs to exist for #! purposes. So renaming it would be bad, but a simlink would work. On Thu, Dec 31, 2015 at 2:27 PM Brock Wilcox <awwa...@thelackthereof.org> wrote: > On Tue, Dec 29, 2015 at 11:39 AM, webmind <webm...@puscii.nl> wrote: > >> >> Yes, wouldn't it make sense to couple the rakudo release version to the >> language it implements? >> > > Naw -- there'll be probably monthly rakudo releases but the Specification > releases should be much less frequent -- like maybe every few months (at > first) or yearly is my guess. > > This might be less confusing if: > * We referred more often to rakudo instead of perl6 when we mean the > implementation (you compile with gcc, not "c"; rakudo confusingly calls > it's interpreter "perl6") > * Get more implementations! If we had like 3-4 implementations to choose > from then it might be more obvious what was going on. > > Probably there would be a stronger argument for the "perl6" binary to be > either renamed to "rakudo" or to be a symlink to whatever your > current-perl6-implementation is were there an alternative implementation > ... but there isn't... so ... I guess someone should do that. :) > > ... though there actually ARE a few others, but none nearly as complete as > Rakudo, afaik > > * https://github.com/sorear/niecza - CLR > * http://fglock.github.io/Perlito/ - Perlito6 written mostly in Perl6 > (lots of other interesting Perlito stuff) > * http://perl6.org/compilers/features - comparison > * several abandoned ones (e.g. Pugs) > > --Brock > >
Re: release?
I also was agreeing with Alex's critique of 6.c and then understanding Patrick's reply. "Semantic Versioning" and Perl 5's versioning scheme is so thoroughly ingrained in me now that 6.c looked like a pre-production release number, and I was waiting for 6.0.0. After reading the explanation, it now looks "normal" to me. Alas there is new confusion. What does the "use v6;" statement at the top of a Perl6 compunit mean? Require a version of the compiler, or semantics of a language spec? It can't mean both, because compiler version numbers eg 6.0.0.1.a are diverging from language spec identifiers eg 6.c. Seems like it would be useful to have different "use" statements to declare needed a certain compiler vs. language semantics, eg use 6.c, 'Perl'; # Use semantics of this spec use 6.0.0, 'Rakudo'; # Require the Rakudo compiler version 6.0.0 or higher use 6; # Require any compiler that implements any Perl 6 -y
Re: release?
On Tue, Dec 29, 2015 at 01:57:57AM -0800, Darren Duncan wrote:
>> On that note, are there going to be Perl 6 versions 6.x.y where {x,y}
are
> > integers? Will 6.0.0 be the first such one? -- Darren Duncan
On Tue, Dec 29, 2015 Patrick Michaud wrote:
> "Perl 6" is a language, not an implementation of that language. Think
of "Perl 6" as being like "C", "C++", "Javascript", etc., where the
language is separate from the (many) implementations of that language.
I'm just a very ordinary perl hacker here, but Alex's point I think should
be addressed. Most of us (i.e ordinary, un-language implementation geeks)
are looking to download a Perl6 and if it's rakudo x.y.z, fine, but make
that seem like something like perl.6.tar.gz. It would seem that gently
introducing the complete separation w/ a little of Perl's famous (to me)
"syntatic sugar" (meta-syntatic?) to help us getting started. Maybe the
lower case distinction, "perl6.x.y" vs "Perl 6.c", would soothe both sides
of the discussion.
But agree that there is a missed opportunity; marketing, audience, ease of
press release noticing, if there's no easy "perl 6" download page. Or,
worse, if there is, but it gets them the text (test suite?) for 6.c
Just a note - currently running the process from:
http://perl6.org/downloads/
and, aside from seeing a number of format argument mismatches [1], seems
to be going well.
a
[1]
e.g.
src/6model/reprs/NFA.c: In function ?nqp_nfa_run?:
src/6model/reprs/NFA.c:442:17: warning: format ?%lld? expects argument of
type ?long long int?, but argument 6 has type ?MVMint64? [-Wformat=]
fprintf(stderr,"%c with %ds target %lx offset
%lld\n",cp,(int)numcur, (long)target, offset);
^
--
Andy Bach
Systems Mangler
Internet: andy_b...@wiwb.uscourts.gov
Voice: (608) 261-5738, Cell: (608) 658-1890
" 'But, when you die, on your death bed,
you will receive total consciousness'...
So I got that goin' for me... which is nice."
Carl Spackler
Re: release?
The understanding of what is going on has certainly become an order or magnitude harder. I personally feel that the way the naming has been done has failed on the "keep easy things easy" part. The C vs GCC example by someone was a good one... C being a specification, and GCC being the compiler with version numbers. However, having a number in the name part of a specification - especially when there was a perl4, perl5 is very very confusing. There is neither consistency with how the "rest of the world" seems to name stuff or continuity with how perl compliers / executables were themselves named. Why not just called Perl 6 something like "AbraCobraDabra" (aka, a completely new thing) - i suspect it's been called Perl 6 because: * The powers that be wanted a "feeling of continuity / relatibility" (as Perl 5 is ubiquitous) and something seen as a "brand new language" would have a higher dropoff in takeup For someone who is new to Perl 6 (but i was a "Perl Programmer" for a long time), i have been thoroughly confused by all the naming - i appreciate that there is much more abstraction of layers now, which is great, but the naming has creating a much higher learning curve to understand what is actually going on... i'm probably still thoroughly wrong on stuff but here is my understanding now (and i admit, i'm far from the sharpest tool in the shed): * Perl 6 is akin to "C" (a specification) (i wish they had called it something completely different though as to be frank, Perl5 to Perl6 looks like a transition between different languages - eg. between Python and Go; there are fundamental differences in notation and the way things are done - i claim no-one looking at some code in perl5 vs perl6 (not knowing either language) would say they were completely different languages) * Perl 6.c is similar to "ANSI C" (an new / upgraded specification) * Rakudo is akin to "GCC" (an implementation of the specification with it's own extensions) * MoarVM / JVM are the VM's that Rakudo can run on (this is an abstraction layer so that we can in the future have different languages talk to each other nicely) * ParrotVM seems to be pretty much dead? (this is not a trolling question, it appears from certain emails on this list in the past few days that this seems to be an opinion, i'm just taking it at face value...) * Panda is akin to CPAN??? * I'm assuming people will develop more VM's - which will lead to: * Better portability between some languages * But also lead to things being implemented differently with nuances that cause massive headaches - ie. Already probably when you move from Rakudo MoarVM to Rakuto JVM, things probably break. I'm assuming JVM stands for Java Virtual Machine - and Rakudo on JVM lets you write Perl 6 code (or should i say "Perl 6.c" or "Rakudo Code"???) that can talk to some of your Java Code easily (including exchanging data objects, etc? - i'd love if someone can indicating if i'm sort of correct with my assumption or totally off the mark... In short, i think i like pretty much everything about Perl 6, except that it's got a number and the words "Perl" in it's name :) simran :) On Tue, Dec 29, 2015 at 10:16 PM, Alex Becker <asb.c...@gmail.com> wrote: > As this is a frequent answer I encounter when having a look at Perl 6, > maybe it's worth having a look at it's message: > > There will be no Perl 6. > There will be no Perl 6 by definition, because Perl 6 is only a > specification. You cannot program a specification. > > Let's call this statement "specimplexpl". > > A pessimist, or simply some random guy looking for a nice, modern > programming language will read the following: > Stop waiting for it. Or asking for it, as you will only get specimplexpl + > (hopefully) the RSS feed with the latest Rakudo* releases. > Learn something useful you could actually use to make a living nowadays, > e.g. C# .NET or Java (the latter if you are in science / public sector). > > > Why, why do we have to fail this way in terms of marketing? > Why do we pray the specimplexpl on the Rakudo* download page at the > begining? Why do we pray the specimplexpl when someone asks for a Perl 6 > implementation (we did get his intention, as it can be seen with the other > answers). > Perl 6 is so cool. You put so much effort into Perl 6. It's like an > offense to all this hard work when telling someone that "there isn't a Perl > 6.x as such". > > > Would it have harmed the holy spec if more people posted a blog post > titled "Perl 6 is out" or "Perl 6 X-Mas release" (like this one: > http://blogs.perl.org/users/damian_conway/2015/12/perl-6-lives.html)? > The specimplexpl can still be done in the body part. Or as a foot note, if > someone will ac
Re: release?
Thanks for all the responses, and I agree with them.
At the same time, I think I was misunderstood, so I will try and clarify my
position now.
1. I fully understand the distinction between a version of the Perl 6 language
spec, or of components thereof (such as of grammar, standard library, test
suite, etc), and a version of a Perl 6 implementation or component thereof (such
as Rakudo, NQP, MoarVM, JVM etc), and a version of a distributing package of the
above (such as Rakudo Star, or Debian packages, or CentOS packages, etc).
2. I advocate such a separation and distinct versioning of such things as the
above. The Rakudo version and Perl 6 spec version are not the same and
shouldn't be.
3. Code written in Perl 6 should declare at least one version of the Perl 6
spec it conforms to and should be treated as, optionally a version it is known
not to conform to, etc. Unlike some other people, I think declaring such a
version the code expects to work with should be mandatory. Each implementation
will either natively support a declared version, or emulate it, or not support
it, etc.
4. As a key point to this discussion, I believe that something as complicated
as the Perl 6 spec itself is bound to have regular updates or bug fixes itself,
where bug means either a documentation mistake or a bug in the test suite etc.
As such, I believe it is perfectly reasonable for the Perl 6 spec itself to have
more finely grained version numbers.
5. Given the prior point, I had until now understood Perl 6.c, 6.d etc, which I
only realized the existence of that scheme in the last month or so, to be
transitional names, and we would use a number-based scheme at some point, for
the language spec itself. Perhaps with a semantic version where incrementing
some numbers added features or possibly removed them, and other numbers just
fixed bugs without being considered a forwards or backwards breaking change.
Here's a question:
If language specifications trail implementations by a significant margin, then
how does Perl 6 code idiomatically declare that it depends on features that say
Rakudo added which aren't in the spec? Does it use an "auth" of "Rakudo" or
something like that? I didn't see your talk so maybe you covered this.
Note, up until now, I had considered using alternate "auth" to indicate a fork
of the spec or such, though in hindsight of your implementations leading spec
comment, I assume this is also how one indicates dependencies on a spec-leading
compiler.
Thank you.
-- Darren Duncan
On 2015-12-29 5:46 AM, Patrick R. Michaud wrote:
On Tue, Dec 29, 2015 at 01:57:57AM -0800, Darren Duncan wrote:
On that note, are there going to be Perl 6 versions 6.x.y where {x,y} are
integers? Will 6.0.0 be the first such one? -- Darren Duncan
This was the topic of my FOSDEM talk last year, and then again at YAPC::NA.
"Perl 6" is a language, not an implementation of that language. Think of "Perl 6" as being like
"C", "C++", "Javascript", etc., where the language is separate from the (many) implementations of
that language.
There are two key points to make:
1. Language specification should follow implementations, not precede them.
This has been found to be true for many programming languages, and it's the way
things work in the Internet RFC/STD process. An update to a language spec
recognizes and ratifies the features that have been largely agreed upon by
implementations and users, as opposed to prescribing what the next version of
the language ought to look like. First is rough consensus, then running code,
and *then* formalization into a specification.
So, if language specification follows implementation, it's not possible for Rakudo or other implementations to use
language version numbers as their primary versioning scheme. To take an example from the C language: My gcc compiler
says it's version 5.2.1, but there's not a version "5.2.1" of the C Programming Language. Similarly, one
doesn't speak of the "C89", "C99", or "C11" release of GCC.
2. It doesn't make a lot of sense to think of major/minor version numbers such as 6.x.y when discussing a language
specification. Compiler releases happen often, incorporating new features, bug fixes, and small incremental changes.
Language specification changes tend to happen on longer timescales -- there's not really a notion of a "minor
release" on such timescales. So, the language specifications are being versioned as "6.a",
"6.b", "6.c", etc., instead of a scheme incorporating minor version increments.
Yes, this separation of language specification and implementation can be unnerving to
those that are so used to Perl 5's tight coupling of the two, including using a common
"version number" for both. But that tight coupling is partly
Re: release?
I think this depends on exactly what you mean by "release".
As others have already said in this thread...
6.c is the current standard for perl and is defined by that branch for
the test suite. The next standard will be called 6.d but it's
probably some way off.
6.c will comprise of a number of monthly releases usually named
2016.01 (after the month) and sometimes .MM.x
I've not seen any use of 6.0.0 typing numbering.
The versioning does seem to cause confusion and this probably needs to
be a FAQ entry
S
On 29 December 2015 at 10:13, Kaare Rasmussen <ka...@jasonic.dk> wrote:
> Hi Darren
>>
>> On that note, are there going to be Perl 6 versions 6.x.y where {x,y} are
>> integers? Will 6.0.0 be the first such one? -- Darren Duncan
>
>
> The next Perl 6 release will be called 6.d. Hopefully it will take a while
> before that happens.
>
> I hope there will be a lot of Rakudo releases in the meantime. I guess the
> next is called 2016.1 ?
>
> /kaare
>
>
>>
>> On 2015-12-29 12:51 AM, Tobias Leich wrote:
>>>
>>> Hi, the first official Perl 6 (the language) release is not called 6.0.0,
>>> it is
>>> called 6.c.
>>> And this is what has been shipped with the Rakudo compiler release
>>> 2015.12.
>>>
>>> Cheers, Tobias
>>>
>>> Am 27.12.2015 um 20:33 schrieb webmind:
>>>>
>>>> Hiya,
>>>>
>>>> I'm a bit confused, there is a major release for Perl 6, but I know
>>>> wonder if this is the 6.0.0 release or when this will be?
>>>>
>>>> Thanks
>>>>
>>>> web
>>>>
>>>
>>>
>>
>
--
4096R/EA75174B Steve Mynott <steve.myn...@gmail.com>
Re: release?
On Tue, Dec 29, 2015 at 01:57:57AM -0800, Darren Duncan wrote:
> On that note, are there going to be Perl 6 versions 6.x.y where {x,y} are
> integers? Will 6.0.0 be the first such one? -- Darren Duncan
This was the topic of my FOSDEM talk last year, and then again at YAPC::NA.
"Perl 6" is a language, not an implementation of that language. Think of "Perl
6" as being like "C", "C++", "Javascript", etc., where the language is separate
from the (many) implementations of that language.
There are two key points to make:
1. Language specification should follow implementations, not precede them.
This has been found to be true for many programming languages, and it's the way
things work in the Internet RFC/STD process. An update to a language spec
recognizes and ratifies the features that have been largely agreed upon by
implementations and users, as opposed to prescribing what the next version of
the language ought to look like. First is rough consensus, then running code,
and *then* formalization into a specification.
So, if language specification follows implementation, it's not possible for
Rakudo or other implementations to use language version numbers as their
primary versioning scheme. To take an example from the C language: My gcc
compiler says it's version 5.2.1, but there's not a version "5.2.1" of the C
Programming Language. Similarly, one doesn't speak of the "C89", "C99", or
"C11" release of GCC.
2. It doesn't make a lot of sense to think of major/minor version numbers such
as 6.x.y when discussing a language specification. Compiler releases happen
often, incorporating new features, bug fixes, and small incremental changes.
Language specification changes tend to happen on longer timescales -- there's
not really a notion of a "minor release" on such timescales. So, the language
specifications are being versioned as "6.a", "6.b", "6.c", etc., instead of a
scheme incorporating minor version increments.
Yes, this separation of language specification and implementation can be
unnerving to those that are so used to Perl 5's tight coupling of the two,
including using a common "version number" for both. But that tight coupling is
partly what led to several of Perl 5's evolutionary dead ends and roadblocks,
and we're trying to avoid repeating that mistake with Perl 6.
Hope this helps.
Pm
On Tue, Dec 29, 2015 at 01:57:57AM -0800, Darren Duncan wrote:
> On that note, are there going to be Perl 6 versions 6.x.y where {x,y} are
> integers? Will 6.0.0 be the first such one? -- Darren Duncan
>
> On 2015-12-29 12:51 AM, Tobias Leich wrote:
> >Hi, the first official Perl 6 (the language) release is not called 6.0.0, it
> >is
> >called 6.c.
> >And this is what has been shipped with the Rakudo compiler release 2015.12.
> >
> >Cheers, Tobias
> >
> >Am 27.12.2015 um 20:33 schrieb webmind:
> >>Hiya,
> >>
> >>I'm a bit confused, there is a major release for Perl 6, but I know
> >>wonder if this is the 6.0.0 release or when this will be?
> >>
> >>Thanks
> >>
> >>web
> >>
> >
> >
>
Re: release?
Hi Darren
On that note, are there going to be Perl 6 versions 6.x.y where {x,y}
are integers? Will 6.0.0 be the first such one? -- Darren Duncan
The next Perl 6 release will be called 6.d. Hopefully it will take a
while before that happens.
I hope there will be a lot of Rakudo releases in the meantime. I guess
the next is called 2016.1 ?
/kaare
On 2015-12-29 12:51 AM, Tobias Leich wrote:
Hi, the first official Perl 6 (the language) release is not called
6.0.0, it is
called 6.c.
And this is what has been shipped with the Rakudo compiler release
2015.12.
Cheers, Tobias
Am 27.12.2015 um 20:33 schrieb webmind:
Hiya,
I'm a bit confused, there is a major release for Perl 6, but I know
wonder if this is the 6.0.0 release or when this will be?
Thanks
web
Re: release?
On that note, are there going to be Perl 6 versions 6.x.y where {x,y} are
integers? Will 6.0.0 be the first such one? -- Darren Duncan
On 2015-12-29 12:51 AM, Tobias Leich wrote:
Hi, the first official Perl 6 (the language) release is not called 6.0.0, it is
called 6.c.
And this is what has been shipped with the Rakudo compiler release 2015.12.
Cheers, Tobias
Am 27.12.2015 um 20:33 schrieb webmind:
Hiya,
I'm a bit confused, there is a major release for Perl 6, but I know
wonder if this is the 6.0.0 release or when this will be?
Thanks
web
Re: release?
As this is a frequent answer I encounter when having a look at Perl 6, maybe it's worth having a look at it's message: There will be no Perl 6. There will be no Perl 6 by definition, because Perl 6 is only a specification. You cannot program a specification. Let's call this statement "specimplexpl". A pessimist, or simply some random guy looking for a nice, modern programming language will read the following: Stop waiting for it. Or asking for it, as you will only get specimplexpl + (hopefully) the RSS feed with the latest Rakudo* releases. Learn something useful you could actually use to make a living nowadays, e.g. C# .NET or Java (the latter if you are in science / public sector). Why, why do we have to fail this way in terms of marketing? Why do we pray the specimplexpl on the Rakudo* download page at the begining? Why do we pray the specimplexpl when someone asks for a Perl 6 implementation (we did get his intention, as it can be seen with the other answers). Perl 6 is so cool. You put so much effort into Perl 6. It's like an offense to all this hard work when telling someone that "there isn't a Perl 6.x as such". Would it have harmed the holy spec if more people posted a blog post titled "Perl 6 is out" or "Perl 6 X-Mas release" (like this one: http://blogs.perl.org/users/damian_conway/2015/12/perl-6-lives.html)? The specimplexpl can still be done in the body part. Or as a foot note, if someone will actually mention that the download link will yield a rakduso.msi file and nor a Perl-6.msi file. The Perl6 home page is a nicder example of how it can be done the right way - it has a "Download Rakudo Perl 6" button. But there however, we fail on the final meters. The latest download is Rakudo Star 2015.09 <http://rakudo.org/downloads/star/rakudo-star-2015.09-x86_64%20%28JIT%29.msi>, I didn't find 2015.12 here: http://rakudo.org/downloads/star/ (or a file named Perl-6-xmas-release.msi, as some kind of fun or an xmas present). There was so much magic about this' years Christmas, as Perl 6 has come out - somehow. And we don't use it. Instead, we still pray: specimplexpl. Everywhere. What do we expect that new interested people are looking for when searching for Perl 6? What do they search for, when they ask about a Perl 6 release? What do they want to download? A spec? A specimplexpl? Or, maybe the successor of Perl 5? In the same relation as Python 2 and Python 3? PHP 4 and PHP 5? SBCL 1.2.7 and SBCL 1.2.14? COBOL-68 and COBOL-2002? TLDR; We fail at Perl 6 marketing. If you are looking for the Perl 6 Christmas release then visit http://perl6.org/downloads/ and try you luck. 2015-12-28 19:41 GMT+01:00 Will Coleda <w...@coleda.com>: > There isn't a 6.0.0 as such. > > Perl 6's language specification, versioned 6.c (aka Christmas) was > released; at the same time, the Rakudo Perl 6 compiler, version > 2015.12 was released, which is the most up to date implementation of > this specification. > > The specification is intended to have only minor changes in 6.c going > forward; the next version (6.d, no specific release date planned) will > likely have more involved changes. In the meantime, an implementation > that supports 6.c is free to change internals or parts of the language > that were not explicitly part of the 6.c specification. > > Future versions of the compiler may have support for multiple versions > of the specification that can be handled with a lexical "use v6.c" to > get old behavior once the spec changes. > > Finally, Rakudo * is a distribution that includes the compiler and > multiple modules; Look for this bundled release of the 2015.12 Rakudo > in the next few days. > > On Sun, Dec 27, 2015 at 2:33 PM, webmind <webm...@puscii.nl> wrote: > > Hiya, > > > > I'm a bit confused, there is a major release for Perl 6, but I know > > wonder if this is the 6.0.0 release or when this will be? > > > > Thanks > > > > web > > > > -- > > GPG Key: https://u2m.nl/data/webmind.asc > > GPG Fingerprint: 0506976E 234653B4 A628EC33 E23D16EE FCF154AE > > XMPP webm...@puscii.nl: D79970A8 7EC43E29 186D86BA 590F20F6 4C7930B8 > > XMPP webm...@laglab.org: 11E91112 091881F7 53EF6108 63C48543 C74D035C > > u2m.nl (exp: 08/04/2016) SHA256: > > > C2:40:67:22:25:52:29:AF:DF:50:4E:2A:6B:32:6D:BC:5B:1E:CA:7D:52:3B:4C:4A:21:5D:C8:E5:AE:7D:1A:09 > > Puscii (exp: 04/03/2016) SHA256: > > > F9:C7:B1:B7:90:6B:17:BF:84:93:93:7C:0F:B4:FD:BE:E3:C0:71:9D:83:01:ED:3A:96:FE:FC:82:9D:30:51:C9 > > > > > > -- > Will "Coke" Coleda >
Re: release?
My understanding is that the happy and long-awaited release announcement was done on Christmas out of tradition of announcing Perl releases on Christmas, that it means that the specification of the language is now declared as (fairly) stable, but the implementation is a different matter. In practical terms, the Rakudo implementation works for me - http://rakudo.org/how-to-get-rakudo/ I use the "rakudobrew" installation tool (on Fedora). Easier-to-install installation packages for various operating systems will probably come in the future. -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore 2015-12-27 21:33 GMT+02:00 webmind <webm...@puscii.nl>: > Hiya, > > I'm a bit confused, there is a major release for Perl 6, but I know > wonder if this is the 6.0.0 release or when this will be? > > Thanks > > web > > -- > GPG Key: https://u2m.nl/data/webmind.asc > GPG Fingerprint: 0506976E 234653B4 A628EC33 E23D16EE FCF154AE > XMPP webm...@puscii.nl: D79970A8 7EC43E29 186D86BA 590F20F6 4C7930B8 > XMPP webm...@laglab.org: 11E91112 091881F7 53EF6108 63C48543 C74D035C > u2m.nl (exp: 08/04/2016) SHA256: > > C2:40:67:22:25:52:29:AF:DF:50:4E:2A:6B:32:6D:BC:5B:1E:CA:7D:52:3B:4C:4A:21:5D:C8:E5:AE:7D:1A:09 > Puscii (exp: 04/03/2016) SHA256: > > F9:C7:B1:B7:90:6B:17:BF:84:93:93:7C:0F:B4:FD:BE:E3:C0:71:9D:83:01:ED:3A:96:FE:FC:82:9D:30:51:C9 > >
Re: release?
On 12/28/2015 01:58 PM, Brock Wilcox wrote: > > Rakudo, as far as I know, passes all of the 6.c tests :). But that > might mean that we need more tests! > Actually, there's a whole bunch of tests declared "TODO" or skipped. But rakudo does pass a vast number of the existing tests.
Re: release?
Rakudo, as far as I know, passes all of the 6.c tests :). But that might mean that we need more tests! On Dec 28, 2015 04:37, "Amir E. Aharoni" <amir.ahar...@gmail.com> wrote: > My understanding is that the happy and long-awaited release announcement > was done on Christmas out of tradition of announcing Perl releases on > Christmas, that it means that the specification of the language is now > declared as (fairly) stable, but the implementation is a different matter. > > In practical terms, the Rakudo implementation works for me - > http://rakudo.org/how-to-get-rakudo/ > > I use the "rakudobrew" installation tool (on Fedora). > > Easier-to-install installation packages for various operating systems will > probably come in the future. > > > -- > Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי > http://aharoni.wordpress.com > “We're living in pieces, > I want to live in peace.” – T. Moore > > 2015-12-27 21:33 GMT+02:00 webmind <webm...@puscii.nl>: > >> Hiya, >> >> I'm a bit confused, there is a major release for Perl 6, but I know >> wonder if this is the 6.0.0 release or when this will be? >> >> Thanks >> >> web >> >> -- >> GPG Key: https://u2m.nl/data/webmind.asc >> GPG Fingerprint: 0506976E 234653B4 A628EC33 E23D16EE FCF154AE >> XMPP webm...@puscii.nl: D79970A8 7EC43E29 186D86BA 590F20F6 4C7930B8 >> XMPP webm...@laglab.org: 11E91112 091881F7 53EF6108 63C48543 C74D035C >> u2m.nl (exp: 08/04/2016) SHA256: >> >> C2:40:67:22:25:52:29:AF:DF:50:4E:2A:6B:32:6D:BC:5B:1E:CA:7D:52:3B:4C:4A:21:5D:C8:E5:AE:7D:1A:09 >> Puscii (exp: 04/03/2016) SHA256: >> >> F9:C7:B1:B7:90:6B:17:BF:84:93:93:7C:0F:B4:FD:BE:E3:C0:71:9D:83:01:ED:3A:96:FE:FC:82:9D:30:51:C9 >> >> >
Re: release?
There isn't a 6.0.0 as such. Perl 6's language specification, versioned 6.c (aka Christmas) was released; at the same time, the Rakudo Perl 6 compiler, version 2015.12 was released, which is the most up to date implementation of this specification. The specification is intended to have only minor changes in 6.c going forward; the next version (6.d, no specific release date planned) will likely have more involved changes. In the meantime, an implementation that supports 6.c is free to change internals or parts of the language that were not explicitly part of the 6.c specification. Future versions of the compiler may have support for multiple versions of the specification that can be handled with a lexical "use v6.c" to get old behavior once the spec changes. Finally, Rakudo * is a distribution that includes the compiler and multiple modules; Look for this bundled release of the 2015.12 Rakudo in the next few days. On Sun, Dec 27, 2015 at 2:33 PM, webmind <webm...@puscii.nl> wrote: > Hiya, > > I'm a bit confused, there is a major release for Perl 6, but I know > wonder if this is the 6.0.0 release or when this will be? > > Thanks > > web > > -- > GPG Key: https://u2m.nl/data/webmind.asc > GPG Fingerprint: 0506976E 234653B4 A628EC33 E23D16EE FCF154AE > XMPP webm...@puscii.nl: D79970A8 7EC43E29 186D86BA 590F20F6 4C7930B8 > XMPP webm...@laglab.org: 11E91112 091881F7 53EF6108 63C48543 C74D035C > u2m.nl (exp: 08/04/2016) SHA256: > C2:40:67:22:25:52:29:AF:DF:50:4E:2A:6B:32:6D:BC:5B:1E:CA:7D:52:3B:4C:4A:21:5D:C8:E5:AE:7D:1A:09 > Puscii (exp: 04/03/2016) SHA256: > F9:C7:B1:B7:90:6B:17:BF:84:93:93:7C:0F:B4:FD:BE:E3:C0:71:9D:83:01:ED:3A:96:FE:FC:82:9D:30:51:C9 > -- Will "Coke" Coleda
release?
Hiya, I'm a bit confused, there is a major release for Perl 6, but I know wonder if this is the 6.0.0 release or when this will be? Thanks web -- GPG Key: https://u2m.nl/data/webmind.asc GPG Fingerprint: 0506976E 234653B4 A628EC33 E23D16EE FCF154AE XMPP webm...@puscii.nl: D79970A8 7EC43E29 186D86BA 590F20F6 4C7930B8 XMPP webm...@laglab.org: 11E91112 091881F7 53EF6108 63C48543 C74D035C u2m.nl (exp: 08/04/2016) SHA256: C2:40:67:22:25:52:29:AF:DF:50:4E:2A:6B:32:6D:BC:5B:1E:CA:7D:52:3B:4C:4A:21:5D:C8:E5:AE:7D:1A:09 Puscii (exp: 04/03/2016) SHA256: F9:C7:B1:B7:90:6B:17:BF:84:93:93:7C:0F:B4:FD:BE:E3:C0:71:9D:83:01:ED:3A:96:FE:FC:82:9D:30:51:C9
Re: release?
Hi webmind I'm a bit confused, there is a major release for Perl 6, but I know wonder if this is the 6.0.0 release or when this will be? I understand your confusion. Most people would expect something downloadable, and there is actually a Rakudo release to go. But 6.c is really the promise that the specs will not change overnight, that it's possible to write a program, or a module, to a spec. The rakudo release is at http://rakudo.org/downloads/rakudo/rakudo-2015.12.tar.gz /kaare
Re: Announce: Rakudo Perl 6 compiler, Development Release #94 (“коледа”)
Bravo Zulu, everyone, and a well-earned rest for Jonathan. The forecast is for scattered scepticism, with occasional outbreaks of trolls, but there should be some positive reaction from the rest of world. On 12/25/15, Will Coleda <w...@coleda.com> wrote: > On behalf of the Rakudo development team, I’m proud to announce the > Christmas release (December 2015) of Rakudo Perl 6 #94 “коледа”. Rakudo > is an implementation of Perl 6 on the Moar Virtual Machine[^1] and the > Java Virtual Machine. > > This is the Christmas release of Rakudo Perl 6. This version of the > compiler > targets the v6.c “Christmas” specification of the Perl 6 language. The > Perl 6 community has been working toward this release over the last 15 > years. > Together, we've built a language that: > > + Retains the core values of Perl: expressiveness, getting the job done, > taking influences from natural language, and pushing the boundaries of > language design > + Has clean, modern syntax, rooted in familiar constructs but revisiting > and revising the things that needed it > + Is truly multi-paradigm, enabling elegant object-oriented, functional, > procedural, and concurrent programming > + Serves as a great glue language, allowing for easy calling of C/C++ > (using NativeCall) and staying compatible with Perl 5 (via > Inline::Perl5). > + Provides composable constructs for working with asynchronous data and > parallel computations > + Dramatically reforms and sets a new standard in regex syntax, which > scales up to full grammars - powerful enough to parse Perl 6 itself > + Has outstanding Unicode support, with strings working at grapheme level > + Values lexical scoping and encapsulation, enabling easy refactoring > + Is extensible through meta-object programming, user-defined operators, > and traits > > The tag for this release is “коледа”[^2], a slavic word for an ancient > winter > festival that has been incorporated into Christmas. We hope you join us > in our celebration of getting our Christmas release shipped! > > While we are extremely happy to ship an official Perl 6 release, this is > not > the end of Rakudo’s development. We will continue to ship monthly releases, > which will continue to improve performance and our user’s experience. We’ll > also continue our work on the specification, with feedback from the > community. > > To be clear on that point, this Rakudo release is not considered the > primary > deliverable for this Christmas; it is the language specification, known > as "roast" (Repository Of All Spec Tests), that is considered the primary > deliverable. The specification tests that define this 6.c version[^3] of > the > language are now frozen, and we hope it will be quite some time before we > feel obligated to define a 6.d (Diwali) version of the language. > > This Rakudo release targets those tests (over 120 thousand of them), and > passes > them all on at least some architectures when the moon is in the right > phase. > But Rakudo itself is not frozen. There is still plenty of work ahead for us > to > improve speed, portability, and stability. Do not expect the level of > perfection that you see in established products. This is essentially a .0 > release of a compiler. We do not claim an absence of bugs or > instabilities. > We do not claim the documentation is complete. We do not claim portability > to > many architectures. We do not claim that all downstream software will work > correctly. Think of it as a first kernel release, and now we get to build > and > port various distributions based around that kernel. > > What we do claim is that you now have a stable language specification, and > you can enjoy getting some stuff done with Perl 6 without us breaking it > every > month—as long as you stick to the features that are actually tested in the > test suite, that is. Please note that any “feature” you discover that is > not tested in the test suite is considered fair game for change without > notice. > > Have the appropriate amount of fun! > > The tarball for this release is available from > <http://rakudo.org/downloads/rakudo/>. > > Please note: This announcement is not for the Rakudo Star > distribution[^4] --- it’s announcing a new release of the compiler > and the specification. For the latest Rakudo Star release, see > <http://rakudo.org/downloads/star/>. A Christmas-based version will > be available soon. > > In addition to being our Christmas release, this is yet another > monthly compiler release; Some of the changes that are new in > release are outlined below: > > New in 2015.12: > + Fixed size and multi-dimensional typed and native arrays > + Great
Announce: Rakudo Perl 6 compiler, Development Release #94 (“коледа”)
On behalf of the Rakudo development team, I’m proud to announce the Christmas release (December 2015) of Rakudo Perl 6 #94 “коледа”. Rakudo is an implementation of Perl 6 on the Moar Virtual Machine[^1] and the Java Virtual Machine. This is the Christmas release of Rakudo Perl 6. This version of the compiler targets the v6.c “Christmas” specification of the Perl 6 language. The Perl 6 community has been working toward this release over the last 15 years. Together, we've built a language that: + Retains the core values of Perl: expressiveness, getting the job done, taking influences from natural language, and pushing the boundaries of language design + Has clean, modern syntax, rooted in familiar constructs but revisiting and revising the things that needed it + Is truly multi-paradigm, enabling elegant object-oriented, functional, procedural, and concurrent programming + Serves as a great glue language, allowing for easy calling of C/C++ (using NativeCall) and staying compatible with Perl 5 (via Inline::Perl5). + Provides composable constructs for working with asynchronous data and parallel computations + Dramatically reforms and sets a new standard in regex syntax, which scales up to full grammars - powerful enough to parse Perl 6 itself + Has outstanding Unicode support, with strings working at grapheme level + Values lexical scoping and encapsulation, enabling easy refactoring + Is extensible through meta-object programming, user-defined operators, and traits The tag for this release is “коледа”[^2], a slavic word for an ancient winter festival that has been incorporated into Christmas. We hope you join us in our celebration of getting our Christmas release shipped! While we are extremely happy to ship an official Perl 6 release, this is not the end of Rakudo’s development. We will continue to ship monthly releases, which will continue to improve performance and our user’s experience. We’ll also continue our work on the specification, with feedback from the community. To be clear on that point, this Rakudo release is not considered the primary deliverable for this Christmas; it is the language specification, known as "roast" (Repository Of All Spec Tests), that is considered the primary deliverable. The specification tests that define this 6.c version[^3] of the language are now frozen, and we hope it will be quite some time before we feel obligated to define a 6.d (Diwali) version of the language. This Rakudo release targets those tests (over 120 thousand of them), and passes them all on at least some architectures when the moon is in the right phase. But Rakudo itself is not frozen. There is still plenty of work ahead for us to improve speed, portability, and stability. Do not expect the level of perfection that you see in established products. This is essentially a .0 release of a compiler. We do not claim an absence of bugs or instabilities. We do not claim the documentation is complete. We do not claim portability to many architectures. We do not claim that all downstream software will work correctly. Think of it as a first kernel release, and now we get to build and port various distributions based around that kernel. What we do claim is that you now have a stable language specification, and you can enjoy getting some stuff done with Perl 6 without us breaking it every month—as long as you stick to the features that are actually tested in the test suite, that is. Please note that any “feature” you discover that is not tested in the test suite is considered fair game for change without notice. Have the appropriate amount of fun! The tarball for this release is available from <http://rakudo.org/downloads/rakudo/>. Please note: This announcement is not for the Rakudo Star distribution[^4] --- it’s announcing a new release of the compiler and the specification. For the latest Rakudo Star release, see <http://rakudo.org/downloads/star/>. A Christmas-based version will be available soon. In addition to being our Christmas release, this is yet another monthly compiler release; Some of the changes that are new in release are outlined below: New in 2015.12: + Fixed size and multi-dimensional typed and native arrays + Greatly overhauled module loading and installation, including handling precompilation at module installation time in Rakudo + while/until loops can now return lists of values + We now catch many more kinds of "Useless use of X in sink context" + A number of convenient Unicode equivalents were introduced + Superscripts can now be used for integer powers + Non-digit unicode characters with a numeric value (½ and such) can now be used for that numeric value + There is a new "approximately equal" operator + Add support for USAGE argument help + Provide tau constant (also: τ) + Can now use channels with supply/react/whenever + Bool is now a proper enum + Supply/Supplier improvements + Use of EVAL now
Announce: Rakudo Star Release 2015.11
On behalf of the Rakudo and Perl 6 development teams, I'm happy to
announce the November 2015 release of "Rakudo Star", a useful and usable
distribution of Perl 6. The tarball for the November 2015 release is
available from <http://rakudo.org/downloads/star/>.
This Rakudo Star release comes with support for the MoarVM
backend (all module tests pass on supported platforms).
In the Perl 6 world, we make a distinction between the language
("Perl 6") and specific implementations of the language such as
"Rakudo Perl". This Star release includes [release 2015.11] of the
[Rakudo Perl 6 compiler], version 2015.11 of [MoarVM], plus various
modules, documentation, and other resources collected from the
Perl 6 community.
[release 2015.11]:
https://github.com/rakudo/rakudo/blob/nom/docs/announce/2015.11.md
[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo
[MoarVM]: http://moarvm.org/
Some of the new compiler features since the ast Rakudo Star release include:
+ There is now an `infix:<.>` operator that does method calls with slightly
looser precedence than the postfix unary method call.
+ New operator `infix o` for function composition
+ `fc` for Unicode-correct case folding implemented
+ grep now accepts :k, :v, :kv, :p attributes
+ `Supply.throttle` for rate-limiting
+ Array.push is now used for pushing one element (mostly); Array.append
exists for pushing multiple values. Same for `unshift`/`prepend`
+ Basic arithmetic operations (`+`, `*`, `-`, `/`) on Range objects
that shift or scale the end points while maintaining exclusions
+ The v notation now allows alphabetic components: v1.2.beta. (Incompatible
because method calls on a version must be protected by \ or () now.)
+ `use v6b+;` notation is now recognized and enforced
+ Many built-in methods that return iterables are now much faster
+ Better error messages when comparing version strings with numbers
+ Several error messages that were lacking line numbers now include them
+ Initial shaped array support
+ `\r\n` (Carriage Return/LineFeed) is now a single (synthetic) grapheme
+ Unicode support adheres to Unicode Annex #29
+ Unicode quotes are now also allowed in regular expressions
+ Improved newline support with "use newline" and updates to IO::Handle
+ Added List.head, List.tail, List.repeated methods
+ Str.encode now allows :replacement parameter for unencodable sequences
+ Str.split now accepts multiple strings to split on
+ New Range.int-bounds returns first/last value for integer ranges
+ Auto-generated meta-ops vivified by referring to them, instead of
executing
+ Illegal assignment of different Numeric values now caught at compile time
+ `` implemented, which returns the routine that `nextsame`
would invoke
+ Many speedups
The Rakudo Perl 6 compiler is now officially in beta for the upcoming
production release around Christmas 2015.
Please note that this release of Rakudo Star is not fully functional
with the
JVM backend from the Rakudo compiler. Please use the MoarVM backend only.
Notable changes in modules shipped with Rakudo Star:
* Bailador: Add MIT License
* DBIish: Improved Windows support
* doc: More documentation; generated HTML is better searchable
* Template::Mustache: Switched from LGPL to Artistic License 2.0
* panda: Default action is no longer `install`; better help messages
* Digest::MD5: Now accepts non-ASCII input (internally encodes as Latin-1)
* LWP::Simple: Support for successful return codes besides 200
* Shell::Command: `which` routine for locating executables
* Updated docs/2015-spw-perl6-course.pdf from Nov 21
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* non-blocking I/O (in progress)
* much of Synopsis 9 and 11
There is an online resource at <http://perl6.org/compilers/features>
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at <rakudo...@perl.org>.
See <http://perl6.org/> for links to much more information about
Perl 6, including documentation, example code, tutorials, reference
materials, specification documents, and other supporting resources. A
Perl 6 tutorial is available as docs/2015-spw-perl6-course.pdf in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
<http://rakudo.org/how-to-help>, ask on the <perl6-compi...@perl.org>
mailing list, or join us on IRC \#perl6 on freenode.
Announce: Rakudo Star Release 2015.09
On behalf of the Rakudo and Perl 6 development teams, I'm excited to
announce the September 2015 release of "Rakudo Star", a useful and
usable distribution of Perl 6. The tarball for the September 2015
release is available from <http://rakudo.org/downloads/star/>.
This Rakudo Star release comes with support for the MoarVM backend (all
module tests pass on supported platforms).
Please note that this release of Rakudo Star is not fully functional
with the JVM backend from the Rakudo compiler. Support should be
restored shortly.
In the Perl 6 world, we make a distinction between the language ("Perl
6") and specific implementations of the language such as "Rakudo Perl".
This Star release includes [release 2015.09] of the [Rakudo Perl 6
compiler], version 2015.09 of [MoarVM], plus various modules,
documentation, and other resources collected from the Perl 6 community.
[release 2015.09]:
https://github.com/rakudo/rakudo/blob/nom/docs/announce/2015.09.md
[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo
[MoarVM]: http://moarvm.org/
Some of the new compiler features added to this release include:
* Great List Refactor (GLR) - See http://design.perl6.org/S07.html
* All Deprecations removed in preparation for Christmas release
* Added support for calling into C++ libraries and calling methods on
C++ classes
* New slurpy parameter, +args or +@args, to allow for one-argument style
binding
* New with/orwith/without conditionals allow you to check for .defined
but topicalize to the actual value returned
* New `supply`, `whenever` and `react` blocks for easy reactive programming
* All Unicode digits can now be part of literal numbers
* `val()` and allomorphic types implemented
* Most European quoting styles are now supported
* New $[...] and ${...} constructs allow prefix itemization
* The .gist and .perl methods can now deal with self-referential structures
Notable changes in modules shipped with Rakudo Star:
* All modules fixed to work with GLR where needed
* Panda now includes JSON::Fast and no longer precompiles to byte code
* Terminal::ANSIColor replaces the deprecated Term::ANSIColor
* New Perl 6 tutorial replaces original perl6 book draft
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* non-blocking I/O (in progress)
* much of Synopsis 9 and 11
There is an online resource at <http://perl6.org/compilers/features>
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at <rakudo...@perl.org>.
See <http://perl6.org/> for links to much more information about
Perl 6, including documentation, example code, tutorials, reference
materials, specification documents, and other supporting resources. A
Perl 6 tutorial is available as docs/2015-spw-perl6-course.pdf in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
<http://rakudo.org/how-to-help>, ask on the <perl6-compi...@perl.org>
mailing list, or join us on IRC \#perl6 on freenode.
Announce: Windows MSI Installers for release 2015.06
The Windows MSI installers are now available, coming again in two versions. One installer targets x86 (32bit) platforms, and the other installer targets x86_64 (64bit) platforms (probably Windows 7 or better). Only the version for x86_64 comes with JIT enabled. The two MSIs are available from http://rakudo.org/downloads/star/.
Announce: Rakudo Star Release 2015.03
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
## A useful, usable, early adopter distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm happy to
announce the March 2015 release of Rakudo Star, a useful and usable
distribution of Perl 6. The tarball for the March 2015 release is
available from http://rakudo.org/downloads/star/.
This Rakudo Star release comes with support for the MoarVM
backend (all module tests pass on supported platforms) along with
experimental support for the JVM backend (the modules `Bailador`,
`Digest::MD5` and `Grammar::Profiler::Simple` are known to fail tests).
In the Perl 6 world, we make a distinction between the language
(Perl 6) and specific implementations of the language such as
Rakudo Perl. This Star release includes [release 2015.03] of the
[Rakudo Perl 6 compiler], version 2015.03 of [MoarVM], plus various
modules, documentation, and other resources collected from the
Perl 6 community.
[release 2015.03]:
https://github.com/rakudo/rakudo/blob/nom/docs/announce/2015.03.md
[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo
[MoarVM]: http://moarvm.org/
Some of the new compiler features added to this release include:
+ several renames of semi-internal methods. Please refer to [the Rakudo
2015.02 release
notes](https://github.com/rakudo/rakudo/blob/nom/docs/announce/2015.03.md)
for the full list
+ Allow `Buf.AT-POS` to return an l-value.
+ Implement `method ^foo($) { ... }` syntax.
+ Implemented [PairMap](http://doc.perl6.org/type/PairMap) (the simple
case only, for now).
+ Implemented `.antipairs` (pairs with value = key).
+ Implemented [pairup](http://doc.perl6.org/type/Any#method_pairup)
for creating pairs from lists.
+ Implemented `LEXICAL`, `OUTERS` and `CALLERS` pseudo-packages
+ Add `array[T]`, usable for native `int`/`num` (MoarVM only for now)
+ Other native improvements, e.g. `my int $a; $a++`
+ Implement `IO::Path.resolve` on r-m/POSIX
In future, the `nqp::` namespace willl only be available after a
declaration
like `use nqp;`.
Changes to modules included in Rakudo Star:
- - [DBIish](https://github.com/perl6/DBIish) supports local Sockets on
mysql,
and now correctly handles returned NULL values in the Pg backend
- - [doc](https://github.com/perl6/doc) ships with much more documentation
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* threads and concurrency (in progress)
* Unicode strings at levels other than codepoints
* interactive readline that understands Unicode
* non-blocking I/O (in progress)
* much of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See http://perl6.org/ for links to much more information about
Perl 6, including documentation, example code, tutorials, reference
materials, specification documents, and other supporting resources. A
draft of a Perl 6 book is available as docs/UsingPerl6-draft.pdf in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC \#perl6 on freenode.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlUN3iYACgkQT81LMIj/VkTYSACfeumxLQzxeRPfNHIYge6ZHEwU
L9sAn0rfiVwi5CB0RSFJ125UKvv5P7OG
=+CBE
-END PGP SIGNATURE-
Announce: Rakudo Star Release 2015.01
# Announce: Rakudo Star Release 2015.01
## A useful, usable, early adopter distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm happy to
announce the January 2015 release of Rakudo Star, a useful and usable
distribution of Perl 6. The tarball for the January 2015 release is
available from http://rakudo.org/downloads/star/.
This Rakudo Star release comes with support for the MoarVM
backend (all module tests pass on supported platforms) along with
experimental support for the JVM backend (some module tests fail).
Three shipped modules are known to fail on Parrot (zavolaj (NativeCall),
jsonrpc and doc)
In the Perl 6 world, we make a distinction between the language
(Perl 6) and specific implementations of the language such as
Rakudo Perl. This Star release includes [release 2015.01.1] of the
[Rakudo Perl 6 compiler], version 7.0.1 of the [Parrot Virtual
Machine], version 2015.01 of [MoarVM], plus various modules,
documentation, and other resources collected from the Perl 6
community.
[release 2015.01.1]:
https://github.com/rakudo/rakudo/blob/nom/docs/announce/2015.01.md
[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo
[Parrot Virtual Machine]: http://parrot.org
[MoarVM]: http://moarvm.org/
Some of the new compiler features added to this release include:
+ Many improvements to Java interop for the JVM backend
+ New simple way of creating an object hash: :{}
+ Substitution now supports assignment meta-op, e.g. s[\d+] += 2
+ Many memory and CPU optimizations
+ Supply.for deprecated in favour of Supply.from-list
Changes to modules included in Rakudo Star:
- [Bailador](https://github.com/tadzik/Bailador) handles POST and URL
params separately
- [DBIish](https://github.com/perl6/DBIish) has improved error reporting
on SQLite
- [doc](https://github.com/perl6/doc) ships with much more documentation
- [panda](https://github.com/tadzik/panda) has a new command `installdeps`
- [Pod::To::HTML](https://github.com/perl6/Pod-To-HTML) now supports
callbacks for code areas
Parrot support will likely be suspended or dropped from future Rakudo
and Rakudo
Star releases, starting with the February or March releases.
In the next Rakudo Star release, modules `Math::RungeKutta` and
`Math::Model`
will likely be dropped. They can still be installed with `panda`.
In future, the `nqp::` namespace willl only be available after a declaration
like `use nqp;'.
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* threads and concurrency (in progress for the JVM and MoarVM backend)
* Unicode strings at levels other than codepoints
* interactive readline that understands Unicode
* non-blocking I/O (in progress for the JVM and MoarVM backend)
* much of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See http://perl6.org/ for links to much more information about
Perl 6, including documentation, example code, tutorials, reference
materials, specification documents, and other supporting resources. A
draft of a Perl 6 book is available as docs/UsingPerl6-draft.pdf in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC \#perl6 on freenode.
Announce: Rakudo Star Release 2014.09
## A useful, usable, early adopter distribution of Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm happy to announce the September 2014 release of Rakudo Star, a useful and usable distribution of Perl 6. The tarball for the September 2014 release is available from http://rakudo.org/downloads/star/. Windows .MSI versions of Rakudo star for the MoarVM and Parrot backend are also avaiable in the downloads area. This Rakudo Star release comes with support for the MoarVM backend (all module tests pass on supported platforms) along with experimental support for the JVM backend (some module tests fail). Two shipped modules are known to fail on Parrot (JSON::RPC and p6doc). In the Perl 6 world, we make a distinction between the language (Perl 6) and specific implementations of the language such as Rakudo Perl. This Star release includes [release 2014.09] of the [Rakudo Perl 6 compiler], version 6.7.0 of the [Parrot Virtual Machine], version 2014.09 of [MoarVM], plus various modules, documentation, and other resources collected from the Perl 6 community. [release 2014.09]: https://github.com/rakudo/rakudo/blob/nom/docs/announce/2014.09.md [Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo [Parrot Virtual Machine]: http://parrot.org [MoarVM]: http://moarvm.org/ Some of the new features added to this release include: * panda (the module installer client) does work on windows again * panda knows about all modules, that are shipped with this release * ./perl6 --profile for MoarVM * Workaround OS X make bug for MoarVM * support for submethod DESTROY (MoarVM only) * optimizations to Str.words, Str.lines, IO.lines, chomp, and return * added experimental support for Proc::Async, MoarVM only for now * Reduced memory size of CORE.setting, improved startup time * startup (on Moar) 15% faster than p5 w/ Moose There are some key features of Perl 6 that Rakudo Star does not yet handle appropriately, although they will appear in upcoming releases. Some of the not-quite-there features include: * advanced macros * threads and concurrency (in progress for the JVM and MoarVM backend) * Unicode strings at levels other than codepoints * interactive readline that understands Unicode * non-blocking I/O * much of Synopsis 9 and 11 There is an online resource at http://perl6.org/compilers/features that lists the known implemented and missing features of Rakudo and other Perl 6 implementations. In many places we've tried to make Rakudo smart enough to inform the programmer that a given feature isn't implemented, but there are many that we've missed. Bug reports about missing and broken features are welcomed at rakudo...@perl.org. See http://perl6.org/ for links to much more information about Perl 6, including documentation, example code, tutorials, reference materials, specification documents, and other supporting resources. A draft of a Perl 6 book is available as docs/UsingPerl6-draft.pdf in the release tarball. The development team thanks all of the contributors and sponsors for making Rakudo Star possible. If you would like to contribute, see http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org mailing list, or join us on IRC \#perl6 on freenode.
Rakudo Star Release 2014.04 - A useful, usable, early adopter distribution of Perl 6
perl6-langu...@perl.org
perl6-compi...@perl.org
parrot-us...@lists.parrot.org
Cc:
Bcc:
Message-Id: 1399313885.8...@jnthn.net
X-Originating-IP: 62.220.188.70
X-Mailer: Webmin 1.550
Date: Mon, 05 May 2014 20:18:05 +0200 (CEST)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=bound1399313885
This is a multi-part message in MIME format.
--bound1399313885
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
# Announce: Rakudo Star Release 2014.04
## A useful, usable, early adopter distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm happy to
announce the April 2014 release of Rakudo Star, a useful and usable
distribution of Perl 6. The tarball for the April 2014 release is
available from http://rakudo.org/downloads/star/. A Windows .MSI
version of Rakudo star will usually appear in the downloads area
shortly after the tarball release.
This is the first Rakudo Star release with support for the MoarVM
backend (all module tests pass on supported platforms) along with
experimental support for the JVM backend (some module tests fail).
In the Perl 6 world, we make a distinction between the language
(Perl 6) and specific implementations of the language such as
Rakudo Perl. This Star release includes [release 2014.04] of the
[Rakudo Perl 6 compiler], version 6.1.0 of the [Parrot Virtual
Machine], version 2014.04 of [MoarVM], plus various modules,
documentation, and other resources collected from the Perl 6
community.
[release 2014.04]:
https://github.com/rakudo/rakudo/blob/nom/docs/announce/2014.04.md
[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo
[Parrot Virtual Machine]: http://parrot.org
[MoarVM]: http://moarvm.org/
Some of the new features added to this release include:
* experimental support for the JVM and MoarVM backends
* NativeCall passes all its tests on all backends
* S17 (concurrency) now in MoarVM (except timing related features)
* winner { more @channels { ... } } now works
* implemented univals(), .unival and .univals (on MoarVM)
* added .minpairs/.maxpairs on (Set|Bag|Mix)Hash
* Naive implementation of is cached trait on Routines
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* threads and concurrency (in work for the JVM and MoarVM backend)
* Unicode strings at levels other than codepoints
* interactive readline that understands Unicode
* non-blocking I/O
* much of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo and
other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See http://perl6.org/ for links to much more information about
Perl 6, including documentation, example code, tutorials, reference
materials, specification documents, and other supporting resources. A
draft of a Perl 6 book is available as docs/UsingPerl6-draft.pdf in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC \#perl6 on freenode.
--bound1399313885--
Rakudo Star Release 2014.03 - A useful, usable, early adopter distribution of Perl 6
# Announce: Rakudo Star Release 2014.03 ## A useful, usable, early adopter distribution of Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm happy to announce the March 2014 release of Rakudo Star, a useful and usable distribution of Perl 6. The tarball for the March 2014 release is available from http://rakudo.org/downloads/star/. A Windows .MSI version of Rakudo star will usually appear in the downloads area shortly after the tarball release. In the Perl 6 world, we make a distinction between the language (Perl 6) and specific implementations of the language such as Rakudo Perl. This Star release includes [release 2014.03] of the [Rakudo Perl 6 compiler], version 6.1.0 of the [Parrot Virtual Machine], plus various modules, documentation, and other resources collected from the Perl 6 community. [release 2014.03]: https://github.com/rakudo/rakudo/blob/nom/docs/announce/2014.03.md [Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo [Parrot Virtual Machine]: http://parrot.org Some of the new features added to this release include: + The core of Rakudo::Debugger is now part of Rakudo itself and works across all backends. + make no longer itemizes its arguments. + for-loops at the statementlist level are now sunk by default. + better parsing of unspaces and formatting codes inside Pod blocks. + Fix for for-loops to be properly lazy + Numerous Pod parsing and formatting improvements + @c as shortcut for @$c, %c as shortcut for %$c + list infix reductions no longer flatten + Numerous compiler suggestion improvements Please note that this release of Rakudo Star does not support the JVM nor the MoarVM backends from the Rakudo compiler. While the other backends mostly implement the same features as the Parrot backend, some bits are still missing that lead to module build problems or test failures. We hope to provide experimental JVM-based and MoarVM-based Rakudo Star releases in April 2014. There are some key features of Perl 6 that Rakudo Star does not yet handle appropriately, although they will appear in upcoming releases. Some of the not-quite-there features include: * advanced macros * threads and concurrency (in work for the JVM and MoarVM backend) * Unicode strings at levels other than codepoints * interactive readline that understands Unicode * non-blocking I/O * much of Synopsis 9 and 11 There is an online resource at http://perl6.org/compilers/features that lists the known implemented and missing features of Rakudo and other Perl 6 implementations. In many places we've tried to make Rakudo smart enough to inform the programmer that a given feature isn't implemented, but there are many that we've missed. Bug reports about missing and broken features are welcomed at rakudo...@perl.org. See http://perl6.org/ for links to much more information about Perl 6, including documentation, example code, tutorials, reference materials, specification documents, and other supporting resources. A draft of a Perl 6 book is available as docs/UsingPerl6-draft.pdf in the release tarball. The development team thanks all of the contributors and sponsors for making Rakudo Star possible. If you would like to contribute, see http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org mailing list, or join us on IRC \#perl6 on freenode.
Announce: Rakudo Star Release 2013.09
## A useful, usable, early adopter distribution of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm happy to
announce the September 2013 release of Rakudo Star, a useful and usable
distribution of Perl 6. The tarball for the September 2013 release is
available from http://rakudo.org/downloads/star/. A Windows .MSI
version of Rakudo star will usually appear in the downloads area
shortly after the tarball release.
In the Perl 6 world, we make a distinction between the language
(Perl 6) and specific implementations of the language such as
Rakudo Perl. This Star release includes [release 2013.09] of the
[Rakudo Perl 6 compiler], version 5.5.0 of the [Parrot Virtual
Machine], plus various modules, documentation, and other resources
collected from the Perl 6 community.
[release 2013.09]:
https://github.com/rakudo/rakudo/blob/nom/docs/announce/2013.09.md
[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo
[Parrot Virtual Machine]: http://parrot.org
Some of the new features added to this release include:
+ candidate argument to bless removed (per spec change)
+ @a.VAR.name and %h.VAR.name implemented
+ The $var.++ and $var.() syntaxes work
+ basics of tr/// implemented
+ Sets/Bags/KeySet/KeyBag now up to spec, except for the empty set
symbol '∅'
This release also contains a range of bug fixes, improvements to error
reporting and better failure modes.
Please note that this release of Rakudo Star does not support the JVM
backend from the Rakudo compiler. While the JVM backend mostly implements
the same features as the Parrot backend, many bits are still missing,
most prominently the native call interface.
We hope to provide a JVM-based Rakudo Star release soon.
The following features have been deprecated or modified from previous
releases due to changes in the Perl 6 specification, and are planned
to be removed or changed as follows:
* `postcircumfix:[ ]` and `postcircumfix:{ }` will become
multi-subs rather than multi-methods *IN THE NEXT RELEASE* of Rakudo
Star. Both at_pos and at_key will remain methods.
* All unary hyper ops currently descend into nested arrays and
hashes. In the future, those operators and methods that are
defined nodal will behave like a one-level map.
* The Str.ucfirst builtin is deprecated; it will be replaced by
Str.tc. In the next Rakudo Star release, use of Str.ucfirst will
actually
generate a warning upon first usage.
* Leading whitespace in rules and under :sigspace will no longer be
converted to `.ws`. For existing regexes that expect this
conversion, add a `?` in front of leading whitespace to make it
meta again.
There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:
* advanced macros
* threads and concurrency
* Unicode strings at levels other than codepoints
* interactive readline that understands Unicode
* non-blocking I/O
* much of Synopsis 9 and 11
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo and
other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.
See http://perl6.org/ for links to much more information about
Perl 6, including documentation, example code, tutorials, reference
materials, specification documents, and other supporting resources. A
draft of a Perl 6 book is available as docs/UsingPerl6-draft.pdf in
the release tarball.
The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC \#perl6 on freenode.
Announce: Rakudo Star 2012.12 release
Announce: Rakudo Star - a useful, usable, early adopter distribution
of Perl 6
On behalf of the Rakudo and Perl 6 development teams, I'm happy to
announce the December 2012 release of Rakudo Star, a useful and
usable distribution of Perl 6. The tarball for the December 2012
release is available from http://rakudo.org/downloads/star/.
A Windows .MSI version of Rakudo star will usually appear in
the downloads area shortly after the tarball release.
In the Perl 6 world, we make a distinction between the language
(Perl 6) and specific implementations of the language such as
Rakudo Perl. This Star release includes release 2012.11 [0] of the
Rakudo Perl 6 compiler [1], version 4.10.0 of the Parrot Virtual
Machine [2], and various modules, documentation, and other
resources collected from the Perl 6 community.
Some of the new features added to this release include:
* Parse errors are much improved, and follow STD, the standard parser,
much more closely; they are more accurate and more information is given
* Rakudo now keeps parsing after some less serious errors
* Better errors for various parse failures
* The junction autothreader is now an order of magnitude faster
* Texas (ASCII) versions of the Set and Bag operators implemented
* Nested Pairs now give correct .perl output
* { a = $_ } now correctly considered a block, not a hash as before
This release also contains a range of performance improvements, bug fixes,
improvements to error reporting and better failure modes.
The following features have been deprecated or modified from previous
releases due to changes in the Perl 6 specification, and are being removed
or changed as follows:
* 'for'-loops will become lazy, and are only evaluated eagerly in
eager or sink (void) context. This means that if a for-loop is
the last statement in a routine, it will usually run after the
routine has returned, so it cannot call return() anymore.
* Unary hyper ops currently descend into nested arrays and hashes.
This will change to make them equivalent to a one-level map.
* The Str.ucfirst builtin is deprecated; it will be replaced by Str.tc.
* Leading whitespace in rules and under :sigspace will no longer be
converted to .ws . For existing regexes that expect this conversion,
add a ? in front of leading whitespace to make it meta again.
* The ?-quantifier on captures in regexes currently binds the capture
slot to a List containing either zero or one Match objects; i.e., it
is equivalent to ** 0..1. In the future, the ?-quantifier will
bind the slot directly to a captured Match or to Nil. Existing code
can manage the transition by changing existing ?-quantifiers to
use ** 0..1, which will continue to return a List of matches.
There are some key features of Perl 6 that Rakudo Star does not
yet handle appropriately, although they will appear in upcoming
releases. Some of the not-quite-there features include:
* advanced macros
* threads and concurrency
* Unicode strings at levels other than codepoints
* interactive readline that understands Unicode
* non-blocking I/O
* much of Synopsis 9
There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo
and other Perl 6 implementations.
In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are
many that we've missed. Bug reports about missing and broken
features are welcomed at rakudo...@perl.org.
See http://perl6.org/ for links to much more information about
Perl 6, including documentation, example code, tutorials, reference
materials, specification documents, and other supporting resources.
A draft of a Perl 6 book is available as docs/UsingPerl6-draft.pdf
in the release tarball.
The development team thanks all of the contributors and sponsors
for making Rakudo Star possible. If you would like to contribute,
see http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC #perl6 on freenode.
[0] https://github.com/rakudo/rakudo/blob/nom/docs/announce/2012.12
[1] http://github.com/rakudo/rakudo
[2] http://parrot.org/
Re: Estimate for next Rakudo Star release?
On Apr 27, 2011, at 5:48 PM, Brian Wisti wrote: --snip-- Is it close? Yes; I was looking for it today. There may be a short additional delay :) Any pressing issues? Not really; just last minute adjustments and additions that are expected when a release has not been cut for 3 months. For example, Parrot has a new garbage collection scheme, and Rakudo knows to select it (instead of the old GC), but Rakudo Star needed to be taught about the new scheme (because Star doesn't use Rakudo's configure to build parrot). Also, the emergency migration of the rakudo.org site is taking up some key people's tuits today. Did I miss an announcement? No; I think that the announcement is waiting on the release itself. Preview: https://github.com/rakudo/star/tree/master/skel/docs/announce/ -- Hope this helps, Bruce Gray (Util on IRC)
Re: Estimate for next Rakudo Star release?
Hi, On Wed, Apr 27, 2011 at 7:36 PM, Bruce Gray bruce.g...@acm.org wrote: [ snippage of useful information ] Thanks for the update! I wanted to make sure I hadn't missed anything. Kind Regards, Brian Wisti http://coolnamehere.com
Re: Production Release - was Re: Questions for Survey about Perl
On 01/05/2011 02:51 PM, Gabor Szabo wrote: Let me just give a probably totally irrelevant comment here. I think most of the open source projects have been in use by many people in production environment before the project had a production release. I guess there are still places that think Linux is not good for their production environment. Probably it is true for all the projects Pm mentioned but a lot of others as well. I remember I was using svn from v0.32 or so. In most technologies I am a very late early adopter. I believe Rakudo and Perl 6 will see a gradual increase in use as they improve, get faster, have more modules etc. It will probably happen a long time before any official 1.0 release will be seen. (if ever) It is very frustrating that the progress is so slow and I can't yet use it for my daily work. It would make both my programming life and my marketing life a lot easier if I could use Rakudo at my clients. But can I seriously complain about the slow progress? Have I made a lot (or any) effort to help Rakudo? I wish I had some time contributing to the effort. Gabor http://szabgab.com/ Maybe we should focus on porting Perl 5 modules on hackathons around the events and blog about the process. Not that I did any serious shot at Perl 6 :-! Regards Racke -- LinuXia Systems = http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP = http://www.icdevgroup.org/ Interchange Development Team
Re: Production Release - was Re: Questions for Survey about Perl
On Thu, 2011-06-01 at 14:53 +0100, Daniel Carrera wrote: I would be very interested to see something that allowed Rakudo to talk to Fortran 95. I am going to use Fortran 95 for my thesis work, and maybe I could write a module to give Rakudo a basic array language. Nothing fancy Is there anything like this for perl5 ? In 2001/2 or so someone asked me to convert their perl implementation of a published algorithm to C. Took two hours to do the prototype from the journal article and the run-time went from 24 hours to 5 minutes. The algorithm was the ruelle-takens algorithm (ca 1979, iirc) to compute the fractal dimension of a series. Application was bioinformatics and the journal was a political science one. Very weird mix. Never had a chance to get back to it but I was thinking that an array module for perl5 would be useful. I probably still have the code stashed somewhere. like MATLAB, NumPy or PDL, but enough to try out algorithms and prototype ideas. As it is, I'll probably use PDL or NumPy for that purpose. -- --gh
Re: Production Release - was Re: Questions for Survey about Perl
On Thu, Jan 6, 2011 at 3:32 PM, Guy Hulbert gwhulb...@eol.ca wrote: On Thu, 2011-06-01 at 14:53 +0100, Daniel Carrera wrote: I would be very interested to see something that allowed Rakudo to talk to Fortran 95. I am going to use Fortran 95 for my thesis work, and maybe I could write a module to give Rakudo a basic array language. Nothing fancy Is there anything like this for perl5 ? Yes, PDL. That's the Perl Data Language. And NumPy is the same thing for Python. The algorithm was the ruelle-takens algorithm (ca 1979, iirc) to compute the fractal dimension of a series. Application was bioinformatics and the journal was a political science one. Very weird mix. Never had a chance to get back to it but I was thinking that an array module for perl5 would be useful. I probably still have the code stashed somewhere. If the algorithm can be expressed largely as array operations, then PDL should give a speed more in the ballpark of the C version. Daniel. -- No trees were destroyed in the generation of this email. However, a large number of electrons were severely inconvenienced.
Re: Production Release - was Re: Questions for Survey about Perl
Wendell Hatcher wendell_hatc...@comcast.net writes: My point is make it a production release so peeps can push it to the powers that be in the corporate world. Valid point. Will http://packages.debian.org/experimental/rakudo be continued? This has been the longest production build in test in the history of mankind. If this was a real world project it would have been dead sometime ago. Don't worry too much. Python 3000 took about 8 years. (Though not sure about betas for testing.) Kind regards, Steffen -- Steffen Schwigon s...@renormalist.net Dresden Perl Mongers http://dresden-pm.org/
Re: Production Release - was Re: Questions for Survey about Perl
Stefan Hornburg (Racke) ra...@linuxia.de writes: Maybe we should focus on porting Perl 5 modules With the current size of CPAN this is IMHO not the way to go. A Perl5 embedding interface is more promising. Pugs had that in a not perfect but usable state. Not sure about Rakudo. An embedded Perl5 in Rakudo would even legitimate a special handling that does not need to be generic in the usual “all foreign-language vs. all Perl6-compilers” standard, because it's about Perl-on-Perl. Once I could easily access CPAN modules I would immediately start using Perl 6 for the daily routine work. The language has everything I need, I just can't hack all the things I regularly use from CPAN. Kind regards, Steffen -- Steffen Schwigon s...@renormalist.net Dresden Perl Mongers http://dresden-pm.org/
Production Release - was Re: Questions for Survey about Perl
So I'd change that to after a production release of a Perl 6 compiler Out of curiosity (because I think it will illuminate some of the difficulty Rakudo devs have in declaring something to be a production release): - What constitues a production release? - What was the first production release of Perl 4? - What was the first production release of Perl 5? - What was the first production release of Linux? - At what point was each of the above declared a production release; was it concurrent with the release, or some time afterwards? Pm Larry responded to a post of mine asking about when Perl6 would be finished - the post was about the time that Pugs was still being actively developed. He pointed to the difference between the waterfall model and the strange attractor model for software development, perl6 progress being measured using the strange attractor model. Many of the questions and answers about a 'production release' imply the waterfall model. The concept here is that some one 'in authority' sets criteria which define 'finished'. Once the software / language / project fulfils the criteria - the edge of the waterfall - it is 'finished'. This has the advantage that everyone knows when to break out the champaign and have a party. It has the disadvantage that criteria of 'finished' can rarely be written in advance because to do so requires precognition, or knowledge of the future. Is there any sophisticated piece of software that is 'perfect', has no bugs, is easy to use? Was MS Vista 'production' quality? Perl 5.0 was quickly replaced by Perl 5.004 (I think), which include references. The strange attractor model implies a process that is never ending, in that there will always be deviations from the solution 'orbit' or 'path'. However, there comes a time when for most normal purposes, the solution orbit will be so 'narrow' that the blips will be not be noticed for most situations. In this respect, qualitative statements such as 'when developers accept it' or 'providers such as ActiveState etc' bundle it are recognition of the strange attractor measure of progress of Perl6. Personally, I think that we are in sight of acceptance for Rakudo Star. This is an implementation of a subset of Perl6. I also believe that when Rakudo begins to implement Sets, Macros and deals with the problems posed by GUI, we will see further changes in the Perl6 specification. It is unlikely that such changes will 'break' Rakudo *. A question that would be useful to ask is: When will Rakudo Star be useful for some of your purposes? a) It is already useful; b) When running precompiled Rakudo * versions for a test suite of example programs is as fast as running Perl5 versions, on average. c) When running (from human readable text to final result) Rakudo * versions for a test suite of example programs is as fast as Perl5 versions, on average. d) When Rakudo * implements a larger subset of Perl6 and/or access well-written C/C++ libraries efficiently, presupposing (c). Another question would be what should be in the test suite of example programs? The example programs are not the test suite, which verifies consistency with the specification. The example programs should be designed - I suggest - to test speed and memory footprint. Ultimately, programmers are interested in solutions that are quick and use least hardware resources (the human resource of writing a simple and understandable program being the strongest part of Perl6, at least I think so).
RE: Production Release - was Re: Questions for Survey about Perl
Hear! Hear! -Original Message- From: Daniel Carrera [mailto:dcarr...@gmail.com] Sent: Wednesday, January 05, 2011 7:15 AM To: Richard Hainsworth Cc: perl6-users@perl.org Subject: Re: Production Release - was Re: Questions for Survey about Perl Although everything you said is technically true, I must point out that without a definitive release, potential users will tend to avoid the software. For people not involved in the process (i.e. 99.995% of Perl users) it is impossible to know when the software is good enough for use. You may talk about strange attractors and orbits, but I haven't the faintest clue how big the orbit of either Perl 6 or Rakudo is. Therefore, I cannot recommend it to other people, and I will hesitate to use it on anything that is very important. Daniel. On Wed, Jan 5, 2011 at 12:38 PM, Richard Hainsworth rich...@rusrating.ru wrote: So I'd change that to after a production release of a Perl 6 compiler Out of curiosity (because I think it will illuminate some of the difficulty Rakudo devs have in declaring something to be a production release): - What constitues a production release? - What was the first production release of Perl 4? - What was the first production release of Perl 5? - What was the first production release of Linux? - At what point was each of the above declared a production release; was it concurrent with the release, or some time afterwards? Pm Larry responded to a post of mine asking about when Perl6 would be finished - the post was about the time that Pugs was still being actively developed. He pointed to the difference between the waterfall model and the strange attractor model for software development, perl6 progress being measured using the strange attractor model. Many of the questions and answers about a 'production release' imply the waterfall model. The concept here is that some one 'in authority' sets criteria which define 'finished'. Once the software / language / project fulfils the criteria - the edge of the waterfall - it is 'finished'. This has the advantage that everyone knows when to break out the champaign and have a party. It has the disadvantage that criteria of 'finished' can rarely be written in advance because to do so requires precognition, or knowledge of the future. Is there any sophisticated piece of software that is 'perfect', has no bugs, is easy to use? Was MS Vista 'production' quality? Perl 5.0 was quickly replaced by Perl 5.004 (I think), which include references. The strange attractor model implies a process that is never ending, in that there will always be deviations from the solution 'orbit' or 'path'. However, there comes a time when for most normal purposes, the solution orbit will be so 'narrow' that the blips will be not be noticed for most situations. In this respect, qualitative statements such as 'when developers accept it' or 'providers such as ActiveState etc' bundle it are recognition of the strange attractor measure of progress of Perl6. Personally, I think that we are in sight of acceptance for Rakudo Star. This is an implementation of a subset of Perl6. I also believe that when Rakudo begins to implement Sets, Macros and deals with the problems posed by GUI, we will see further changes in the Perl6 specification. It is unlikely that such changes will 'break' Rakudo *. A question that would be useful to ask is: When will Rakudo Star be useful for some of your purposes? a) It is already useful; b) When running precompiled Rakudo * versions for a test suite of example programs is as fast as running Perl5 versions, on average. c) When running (from human readable text to final result) Rakudo * versions for a test suite of example programs is as fast as Perl5 versions, on average. d) When Rakudo * implements a larger subset of Perl6 and/or access well-written C/C++ libraries efficiently, presupposing (c). Another question would be what should be in the test suite of example programs? The example programs are not the test suite, which verifies consistency with the specification. The example programs should be designed - I suggest - to test speed and memory footprint. Ultimately, programmers are interested in solutions that are quick and use least hardware resources (the human resource of writing a simple and understandable program being the strongest part of Perl6, at least I think so). -- No trees were destroyed in the generation of this email. However, a large number of electrons were severely inconvenienced. -- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review
Re: Production Release - was Re: Questions for Survey about Perl
There has been requests and talk of a production release for years now. Fancy titles released have come out monthly and quarterly for some time. At some point you have to say it simply isn't a good product or it is going to production how long are we going to hear excuses of my dog died past week and the production release is delayed for a year. Perl 6 at this point seems like a bad dream at best and there really isn't a need since moose and perl 5 have improved. Sent from my iPhone Wendell Hatcher wendell_hatc...@comcast.net 303-520-7554 Blogsite: http://thoughtsofaperlprogrammer.typepad.com/blog On Jan 5, 2011, at 6:13 AM, Anderson, Jim jim.ander...@bankofamerica.com wrote: Hear! Hear! -Original Message- From: Daniel Carrera [mailto:dcarr...@gmail.com] Sent: Wednesday, January 05, 2011 7:15 AM To: Richard Hainsworth Cc: perl6-users@perl.org Subject: Re: Production Release - was Re: Questions for Survey about Perl Although everything you said is technically true, I must point out that without a definitive release, potential users will tend to avoid the software. For people not involved in the process (i.e. 99.995% of Perl users) it is impossible to know when the software is good enough for use. You may talk about strange attractors and orbits, but I haven't the faintest clue how big the orbit of either Perl 6 or Rakudo is. Therefore, I cannot recommend it to other people, and I will hesitate to use it on anything that is very important. Daniel. On Wed, Jan 5, 2011 at 12:38 PM, Richard Hainsworth rich...@rusrating.ru wrote: So I'd change that to after a production release of a Perl 6 compiler Out of curiosity (because I think it will illuminate some of the difficulty Rakudo devs have in declaring something to be a production release): - What constitues a production release? - What was the first production release of Perl 4? - What was the first production release of Perl 5? - What was the first production release of Linux? - At what point was each of the above declared a production release; was it concurrent with the release, or some time afterwards? Pm Larry responded to a post of mine asking about when Perl6 would be finished - the post was about the time that Pugs was still being actively developed. He pointed to the difference between the waterfall model and the strange attractor model for software development, perl6 progress being measured using the strange attractor model. Many of the questions and answers about a 'production release' imply the waterfall model. The concept here is that some one 'in authority' sets criteria which define 'finished'. Once the software / language / project fulfils the criteria - the edge of the waterfall - it is 'finished'. This has the advantage that everyone knows when to break out the champaign and have a party. It has the disadvantage that criteria of 'finished' can rarely be written in advance because to do so requires precognition, or knowledge of the future. Is there any sophisticated piece of software that is 'perfect', has no bugs, is easy to use? Was MS Vista 'production' quality? Perl 5.0 was quickly replaced by Perl 5.004 (I think), which include references. The strange attractor model implies a process that is never ending, in that there will always be deviations from the solution 'orbit' or 'path'. However, there comes a time when for most normal purposes, the solution orbit will be so 'narrow' that the blips will be not be noticed for most situations. In this respect, qualitative statements such as 'when developers accept it' or 'providers such as ActiveState etc' bundle it are recognition of the strange attractor measure of progress of Perl6. Personally, I think that we are in sight of acceptance for Rakudo Star. This is an implementation of a subset of Perl6. I also believe that when Rakudo begins to implement Sets, Macros and deals with the problems posed by GUI, we will see further changes in the Perl6 specification. It is unlikely that such changes will 'break' Rakudo *. A question that would be useful to ask is: When will Rakudo Star be useful for some of your purposes? a) It is already useful; b) When running precompiled Rakudo * versions for a test suite of example programs is as fast as running Perl5 versions, on average. c) When running (from human readable text to final result) Rakudo * versions for a test suite of example programs is as fast as Perl5 versions, on average. d) When Rakudo * implements a larger subset of Perl6 and/or access well-written C/C++ libraries efficiently, presupposing (c). Another question would be what should be in the test suite of example programs? The example programs are not the test suite, which verifies consistency with the specification. The example programs should be designed - I suggest - to test speed and memory footprint. Ultimately, programmers are interested
Re: Production Release - was Re: Questions for Survey about Perl
On Wed, Jan 5, 2011 at 17:30, Guy Hulbert gwhulb...@eol.ca wrote: Rakudo is not listed here: http://shootout.alioth.debian.org/ Fixing that is something I'd like to help with. Note that go was listed *before* it was announced. That tells me that the go authors are, in some small way, more serious about their project succeeding than perl6. So your suggestion to Gabor is to add the question: Do you think that NOT listing Rakudo at shootout.alioth.debian.org means Rakudo is not a serious project? Or did you have some other point? (This is the first time I've seen shootout.alioth.debian.org, I won't claim that it's not a serious shootout just because of that, BTW.) -- Jan
Re: Production Release - was Re: Questions for Survey about Perl
My point is make it a production release so peeps can push it to the powers that be in the corporate world. This has been the longest production build in test in the history of mankind. If this was a real world project it would have been dead sometime ago. Sent from my iPhone Wendell Hatcher wendell_hatc...@comcast.net 303-520-7554 Blogsite: http://thoughtsofaperlprogrammer.typepad.com/blog On Jan 5, 2011, at 9:31 AM, Richard Hainsworth rich...@rusrating.ru wrote: Without the development phenomenon of Perl6, it's difficult to see how Moose and other improvements in perl 5 would have occurred. Despite the frustrations in following the growth of Pugs, then Rakudo, it's been fun, worthwhile and inspiring. A bit like life really. Do you really want it to end? But until it ends, how can you tell what sort of person you are, or what your achievements have been? I love Perl6. Rukudo is great - already. On 01/05/11 17:21, Wendell Hatcher wrote: There has been requests and talk of a production release for years now. Fancy titles released have come out monthly and quarterly for some time. At some point you have to say it simply isn't a good product or it is going to production how long are we going to hear excuses of my dog died past week and the production release is delayed for a year. Perl 6 at this point seems like a bad dream at best and there really isn't a need since moose and perl 5 have improved. Sent from my iPhone Wendell Hatcher wendell_hatc...@comcast.net 303-520-7554 Blogsite: http://thoughtsofaperlprogrammer.typepad.com/blog On Jan 5, 2011, at 6:13 AM, Anderson, Jimjim.ander...@bankofamerica.com wrote: Hear! Hear! -Original Message- From: Daniel Carrera [mailto:dcarr...@gmail.com] Sent: Wednesday, January 05, 2011 7:15 AM To: Richard Hainsworth Cc: perl6-users@perl.org Subject: Re: Production Release - was Re: Questions for Survey about Perl Although everything you said is technically true, I must point out that without a definitive release, potential users will tend to avoid the software. For people not involved in the process (i.e. 99.995% of Perl users) it is impossible to know when the software is good enough snip
Re: Production Release - was Re: Questions for Survey about Perl
On 01/05/11 19:48, Daniel Carrera wrote: On Wed, Jan 5, 2011 at 5:05 PM, Richard Hainsworthrich...@rusrating.ru wrote: It is blindingly obvious that the majority of language users, ..., will only start to use a language when it is recommended by 'those in authority'... I think the issue of a version number is irrelevant 1) You have more or less contradicted yourself. If we agree that Larry Wall is an authority, for example, it is reasonable to wait until he says that the Perl 6 spec is ready, and many will also wait until Rakudo claims to mostly comply with the Perl 6 spec. From what Larry has already said, I dont think he ever will say the Perl 6 spec is ready. The spec and the language are evolving together. That is what the waterfall and attractor stuff was all about. When I said 'in authority', I meant those opinion-makers (from bloggers to journalists to heads of major software developers) who start saying 'xxx is a really cool language'. 2) Version number may not be relevant to you, but it is relevant to others. Therefore, it is relevant to the adoption of Perl 6. And here it seems to me that you begin to prove the point I am trying to make: version numbers are irrelevant as carriers of information about usefulness, stability, or even maturity of product. , given the vested interest of the developer to assign a number that will attract users, That has not been my experience with FOSS projects. Rather, I think developers shy away from ever saying 1.0. For example, the JED editor has been around for a long time, but its version number is 0.99-19. How can 0.99-19 mean anything? Does it mean under 1.0? If so, does this meant that the developers of JED consider it to be unusable or 'not for production purposes'? My entire point is that the version number, in of itself, has no more meaning than what the developers want it to mean. But acceptance is not determined by the developers. The Enlightenment window manager too 10 years before they were comfortable saying 1.0. This fear of 1.0 was even the subject of a paragraph in Eric Raymond's The Cathedral and The Bazaar. to such an extent that there is rule of thumb never to use the first release, but to wait until the version 'has matured'. I've heard this in the Windows world, Though I have been using Linux exclusively for about 5 years now, the Windows world remains an order of magnitude larger. So again, if the point is true in the Windows world, it seems I would win the argument. but I think the FOSS world version numbers tend to be lower. For example, I remember that Netscape 5.0 was equivalent to Mozilla 1.0. Wasnt that due to organisational and ownership changes relating to the development of Netscape? Even if the developers of Rakudo release a V1.0, would that in itself lead to the acceptance of Perl6. I doubt it. Necessary but not sufficient condition? Not even necessary. Why not v0.99-? A great deal that is needed to demonstrate the stability and strength of Perl6 for 'production' purposes has been included in the design from the very beginning, namely, a MASSIVE test suite. How many people, not involved in Perl 6, know that? See the point? I bet that you don't follow the development process of every single software package you use. For any given software package, 99.99% of users do not follow the developers list of look through the test suite. You are again confirming a point I have tried to make. Most people do not themselves try out new languages or indeed anything new until they have read a recommendation from someone they trust. If I want a new camera, I search the internet for reviews - I cant test each one. But once I do settle on a choice, I then want the proof. Just because a reviewer says its good, how do I know he / she isnt paid by the company? The proof that software is stable and robust comes from testing. And testing has been the foundation of the development of Perl6. When - eventually - critics compare Perl6 to some other language and discuss the robustness of the compiler, they will look at the size of the test suites. Richard Daniel.
Re: Production Release - was Re: Questions for Survey about Perl
On Wed, 2011-05-01 at 10:24 -0700, Wendell Hatcher wrote: I have to agree I don't think this is a serious project. In-fact at this point it seems like a bunch of friends working on a hobby in their basement. I'm not sure I said anything to agree with. You seem to misinterpret my intention. [snip] Do you think that NOT listing Rakudo at shootout.alioth.debian.org means Rakudo is not a serious project? Or did you have some other point? Marketing. What I meant was that a serious project pays attention to marketing. The perl6 marketing effort is limited by resources more than go is. [snip] The benchmarking program can be downloaded (which I've done) and comes bundled with 2 or 3 python programs, one of which requires python 2.5 and I'm still on python 2.4 (don't ask). However I've figured out how to see the source for example programs, so I'll manually download all the perl5 and C ones and try to get the benchmarker going for those. Here's what I will attempt to reproduce: http://shootout.alioth.debian.org/u32/benchmark.php?test=alllang=perllang2=gcc I will start by downloading each program in C and perl (there seem to be several C versions -- and sometimes several perl versions available) and just running them appropriately. It'll take me a little while ... I'm fairly busy. I'll report _any_ progress back to the list ... if you don't hear from me by February 1st feel free to nag me. By 'progress', I mean something on github. -- --gh
Re: Production Release - was Re: Questions for Survey about Perl
'serious project' ??? For some 'serious' people, Perl6 is a 'serious project'. Concepts of 'serious' differ amongst reasonable people. Not a problem if your 'serious' aint my 'serious'. As an aside, it took 358 years to prove Fermat's Last Theorem. Wiles - who proved it - shut himself away for the five years he spent creating the last part of the proof sequence. A number of historical figures have looked at the problem. That to my mind is a 'serious project' and serious people, and Wiles did indeed work on it in a 'basement' as a 'hobby'. It was an obsession and he was afraid of telling people what he was working on. But now we consider him a hero. Rakudo and Perl6 is being developed in the way it is for good and practical reasons. Richard On 01/05/11 20:24, Wendell Hatcher wrote: I have to agree I don't think this is a serious project. In-fact at this point it seems like a bunch of friends working on a hobby in their basement. Sent from my iPhone Wendell Hatcher wendell_hatc...@comcast.net 303-520-7554 Blogsite: http://thoughtsofaperlprogrammer.typepad.com/blog On Jan 5, 2011, at 10:15 AM, Guy Hulbertgwhulb...@eol.ca wrote: On Wed, 2011-05-01 at 18:02 +0100, Jan Ingvoldstad wrote: On Wed, Jan 5, 2011 at 17:30, Guy Hulbertgwhulb...@eol.ca wrote: Rakudo is not listed here: http://shootout.alioth.debian.org/ Fixing that is something I'd like to help with. Note that go was listed *before* it was announced. That tells me that the go authors are, in some small way, more serious about their project succeeding than perl6. So your suggestion to Gabor is to add the question: No. The subject changed ... Do you think that NOT listing Rakudo at shootout.alioth.debian.org means Rakudo is not a serious project? Or did you have some other point? Marketing. (This is the first time I've seen shootout.alioth.debian.org, I won't claim that it's not a serious shootout just because of that, BTW.) When go was announced a link to 'shootout' was in the announcement. I think I might have seen if before that but, if so, i'd forgotten so it was new to me at the time. What got me interested in perl6 was the april fools announcement about parrot ostensibly by Larry and Guido. Something like 10 years ago. I don't learn new programming languages unless I have something to do with it. I've been looking at what it would take to implement perl6/rakudo versions of the programs on 'shootout', and I think I can do it so I will try to get one or two of them running properly in the benchmarker. The benchmarking program can be downloaded (which I've done) and comes bundled with 2 or 3 python programs, one of which requires python 2.5 and I'm still on python 2.4 (don't ask). However I've figured out how to see the source for example programs, so I'll manually download all the perl5 and C ones and try to get the benchmarker going for those. It'll take me a little while ... -- --gh
Re: Production Release - was Re: Questions for Survey about Perl
Guy, Your idea is actually exactly what I was suggesting when I said 'example programs'. I think there are/were perl6 versions for the shootout problems. I am not sure what happened to them. Getting benchmarking will be interesting. Regards, Richard On 01/05/11 20:15, Guy Hulbert wrote: On Wed, 2011-05-01 at 18:02 +0100, Jan Ingvoldstad wrote: On Wed, Jan 5, 2011 at 17:30, Guy Hulbertgwhulb...@eol.ca wrote: Rakudo is not listed here: http://shootout.alioth.debian.org/ Fixing that is something I'd like to help with. Note that go was listed *before* it was announced. That tells me that the go authors are, in some small way, more serious about their project succeeding than perl6. So your suggestion to Gabor is to add the question: No. The subject changed ... Do you think that NOT listing Rakudo at shootout.alioth.debian.org means Rakudo is not a serious project? Or did you have some other point? Marketing. (This is the first time I've seen shootout.alioth.debian.org, I won't claim that it's not a serious shootout just because of that, BTW.) When go was announced a link to 'shootout' was in the announcement. I think I might have seen if before that but, if so, i'd forgotten so it was new to me at the time. What got me interested in perl6 was the april fools announcement about parrot ostensibly by Larry and Guido. Something like 10 years ago. I don't learn new programming languages unless I have something to do with it. I've been looking at what it would take to implement perl6/rakudo versions of the programs on 'shootout', and I think I can do it so I will try to get one or two of them running properly in the benchmarker. The benchmarking program can be downloaded (which I've done) and comes bundled with 2 or 3 python programs, one of which requires python 2.5 and I'm still on python 2.4 (don't ask). However I've figured out how to see the source for example programs, so I'll manually download all the perl5 and C ones and try to get the benchmarker going for those. It'll take me a little while ...
Re: Production Release - was Re: Questions for Survey about Perl
On Wed, 2011-05-01 at 20:51 +0300, Richard Hainsworth wrote: 'serious project' ??? For some 'serious' people, Perl6 is a 'serious project'. Concepts of 'serious' differ amongst reasonable people. Not a problem if your 'serious' aint my 'serious'. For programming languages, there are rankings by number of developers. A Historical Example DateNumber 19791 198016 198138 198285 1983??+2 1984??+50 1985500 19862,000 19874,000 198815,000 198950,000 1990150,000 1991400,000 Taken from the language author's Design and Evolution book. Chapter 7. My wife was sent on a course to learn this language in the early 1990s. So you have about 10 years to get started. -- --gh
Announce: Rakudo Perl 6 compiler development release #31 (Atlanta)
On behalf of the Rakudo development team, I'm happy to announce the
July 2010 development release of Rakudo Perl #31 Atlanta.
Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine
(see http://www.parrot.org). The tarball for the July 2010 release
is available from http://github.com/rakudo/rakudo/downloads.
Please note: This is not the Rakudo Star release, which is scheduled
for July 29, 2010 [1]. The Star release will include the compiler, an
installer, modules, a book (PDF), and more.
The Rakudo Perl compiler follows a monthly release cycle, with each release
named after a Perl Mongers group. The July 2010 release is code named
Atlanta in recognition of Atlanta.pm and their Perl 5 Phalanx project [2],
which they selected for its benefits to Perl 6.
Some of the specific changes and improvements occurring with this
release include:
* Rakudo now properly constructs closures in most instances.
* Undefined objects can now autovivify into arrays or hashes when
subscripted with .[ ] or .{ } .
* Arrays can now handle infinite ranges.
* Generic, multi-level Whatever-currying now works, e.g. (1, 1, *+* ... *).
* The REPL shell now remembers lexical declarations in susbsequent lines.
* The open() subroutine now returns a Failure instead of throwing
a fatal exception.
* Rakudo now provides $*ARGFILES for reading from files specified
on the command line.
* Added $*PERL, moved %*VM to $*VM.
* Simple binding operators := and ::= now work.
* Simple feed operators == and == now work.
For a more detailed list of changes see docs/ChangeLog.
The development team thanks all of our contributors and sponsors for
making Rakudo Perl possible, as well as those people who worked on parrot, the
Perl 6 test suite and the specification.
The following people contributed to this release:
Patrick R. Michaud, Jonathan Worthington, Moritz Lenz, Solomon Foster,
Carl Masak, Bruce Gray, Martin Berends, chromatic, Will Coke Coleda,
Matthew (lue), Timothy Totten, maard, Kodi Arfer, TimToady, Stephen Weeks,
Patrick Abi Salloum, snarkyboojum, Radu Stoica, Vyacheslav Matjukhin,
Andrew Whitworth, cognominal, Tyler Curtis, Alex Kapranoff, Ingy döt Net,
Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯, mathw, lue, Вячеслав Матюхин
If you would like to contribute, see http://rakudo.org/how-to-help, ask on
the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode.
The next release of Rakudo (#32) is scheduled for August 19, 2010.
A list of the other planned release dates and code names for 2010 is
available in the docs/release_guide.pod file. In general, Rakudo
development releases are scheduled to occur two days after each
Parrot monthly release. Parrot releases the third Tuesday of each month.
Have fun!
[1] http://rakudo.org/node/73
[2] http://code.google.com/p/atlanta-pm-code/
--
Will Coke Coleda
Announce: Rakudo Perl 6 development release #30 (Kiev)
On behalf of the Rakudo development team, I'm pleased to announce the June 2010 development release of Rakudo Perl #30 Kiev. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine (see http://www.parrot.org). The tarball for the June 2010 release is available from http://github.com/rakudo/rakudo/downloads. Rakudo Perl follows a monthly release cycle, with each release named after a Perl Mongers group. This release is named after the Perl Mongers from the beautiful Ukrainian capital, Kiev. They recently helped organize and participated in the Perl Mova + YAPC::Russia conference, the хакмит (hackathon) of which was a particular success for Rakudo. All those who joined the Rakudo hacking - from Kiev and further afield - contributed spec tests as well as patches to Rakudo, allowing various RT tickets to be closed, and making this month's release better. Дякую! Some of the specific changes and improvements occurring with this release include: * Rakudo now uses immutable iterators internally, and generally hides their existence from programmers. Many more things are now evaluated lazily. * Backtraces no longer report routines from Parrot internals. This used to be the case in the Rakudo alpha branch as well, but this time they are also very pleasant to look at. * Match objects now act like real hashes and arrays. * Regexes can now interpolate variables. * Hash and array slicing has been improved. * The REPL shell now prints results, even when not explicitly asked to print them, thus respecting the P part of REPL. * Rakudo now passes 33,378 spectests. We estimate that there are about 39,900 tests in the test suite, so Rakudo passes about 83% of all tests. For a more detailed list of changes see docs/ChangeLog. The development team thanks all of our contributors and sponsors for making Rakudo Perl possible, as well as those people who worked on parrot, the Perl 6 test suite and the specification. The following people contributed to this release: Patrick R. Michaud, Moritz Lenz, Jonathan Worthington, Solomon Foster, Patrick Abi Salloum, Carl Mäsak, Martin Berends, Will Coke Coleda, Vyacheslav Matjukhin, snarkyboojum, sorear, smashz, Jimmy Zhuo, Jonathan Duke Leto, Maxim Yemelyanov, Stéphane Payrard, Gerd Pokorra, cognominal, Bruce Keeler, Ævar Arnfjörð Bjarmason, Shrivatsan, Hongwen Qiu, quester, Alexey Grebenschikov, Timothy Totten If you would like to contribute, see http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#31) is scheduled for July 22, 2010. A list of the other planned release dates and code names for 2010 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun!
Rakudo Perl 6 development release #28 (Moscow)
On behalf of the Rakudo development team, I'm pleased to announce the March 2010 development release of Rakudo Perl #28 Moscow. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine (see http://www.parrot.org). The tarball for the April 2010 release is available from http://github.com/rakudo/rakudo/downloads . Rakudo Perl follows a monthly release cycle, with each release named after a Perl Mongers group. The April 2010 release is code named Moscow in recognition of Москва.пм and their invitation of Jonathan Worthington, one of our core develepors, to speak at the Russian Internet Technologies 2010 [1] conference. Some of the specific changes and improvements occuring with this release include: * Expressions that begin with a variable and end with a circumfix now properly interpolate into double-quoted strings, like @array.sort() or %hashkey. * Item assignment now has tighter precdence than list assignment, so both 'my @a = 1, 2, 3' and '$a = 1, $b = 2' magically work. * Most of the DateTime built-in type has been backported from the alpha branch, and is now accompanied by a Date type for date-only calculations. * Many obsolete uses of Perl 5 constructs are now caught and give helpful error messages. * As always, many additional small features and bug fixes make working with Rakudo more pleasant. * Rakudo now passes 30,931 spectests. We estimate that there are about 39,000 tests in the test suite, so Rakudo passes about 79% of all tests. For a more detailed list of changes see docs/ChangeLog. The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#29) is scheduled for May 20, 2010. A list of the other planned release dates and code names for 2010 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun!
Announce: Rakudo Perl 6 development release #27 (Copenhagen)
Announce: Rakudo Perl 6 development release #27 (Copenhagen) On behalf of the Rakudo development team, I'm pleased to announce the March 2010 development release of Rakudo Perl #27 Copenhagen. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine (see http://www.parrot.org). The tarball for the March 2010 release is available from http://github.com/rakudo/rakudo/downloads . Rakudo Perl follows a monthly release cycle, with each release named after a Perl Mongers group. The March 2010 release is code named Copenhagen for Copenhagen.pm, hosts of the Perl 6 Copenhagen Hackathon [1], which took place in connection with the Open Source Days Conference. The main goal of the hackathon was to raise some awareness around Perl 6, and to give everyone a chance to get their hands-on with Perl 6. The Copenhagen hackathon helped nail down a number of issues regarding module loading. During these days we also saw a heightened activity on the channel, in the Perl 6 and Rakudo repositories, and in the number of passing tests. All this was contributed by people both on location and elsewhere. The RT queue peaked at 725 new/open tickets, and then started on a downward trend. Apart from the great steps forward in productivity, it was the first time some of the core Perl 6 contributors had a chance to meet. Some of the specific changes and improvements occuring with this release include: * Numerous updates to trigonometric functions and the Rat class * Basic s/// and s[...] = '...' implemented * use improved and need/import implemented, with some basic support for versioned modules and lexical importation * Grammars work again and now include support for regexes taking parameters and proto-regexes * Series operator now has basic support for the current Spec. * User defined operators working again * Support, though with caveats, for !, R, X and Z meta-operators * Performance improvements for invocation and hash creation * Various parsing bugs fixed * Variables initialized to Any by default now, not Mu * ROADMAP updates For a more detailed list of changes see docs/ChangeLog. The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#28) is scheduled for April 22, 2010. A list of the other planned release dates and codenames for 2010 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! [1] http://conferences.yapceurope.org/hack2010dk/
Re: Announce: Rakudo Perl 6 development release #27 (Copenhagen)
Is there a production release date? Sent from my iPhone Wendell Hatcher wendell_hatc...@comcast.net 303-520-7554 Blogsite: http://thoughtsofaperlprogrammer.vox.com/ On Mar 18, 2010, at 11:47 AM, Nuno 'smash' Carvalho sm...@cpan.org wrote: Announce: Rakudo Perl 6 development release #27 (Copenhagen) On behalf of the Rakudo development team, I'm pleased to announce the March 2010 development release of Rakudo Perl #27 Copenhagen. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine (see http://www.parrot.org). The tarball for the March 2010 release is available from http://github.com/rakudo/rakudo/downloads . Rakudo Perl follows a monthly release cycle, with each release named after a Perl Mongers group. The March 2010 release is code named Copenhagen for Copenhagen.pm, hosts of the Perl 6 Copenhagen Hackathon [1], which took place in connection with the Open Source Days Conference. The main goal of the hackathon was to raise some awareness around Perl 6, and to give everyone a chance to get their hands-on with Perl 6. The Copenhagen hackathon helped nail down a number of issues regarding module loading. During these days we also saw a heightened activity on the channel, in the Perl 6 and Rakudo repositories, and in the number of passing tests. All this was contributed by people both on location and elsewhere. The RT queue peaked at 725 new/open tickets, and then started on a downward trend. Apart from the great steps forward in productivity, it was the first time some of the core Perl 6 contributors had a chance to meet. Some of the specific changes and improvements occuring with this release include: * Numerous updates to trigonometric functions and the Rat class * Basic s/// and s[...] = '...' implemented * use improved and need/import implemented, with some basic support for versioned modules and lexical importation * Grammars work again and now include support for regexes taking parameters and proto-regexes * Series operator now has basic support for the current Spec. * User defined operators working again * Support, though with caveats, for !, R, X and Z meta-operators * Performance improvements for invocation and hash creation * Various parsing bugs fixed * Variables initialized to Any by default now, not Mu * ROADMAP updates For a more detailed list of changes see docs/ChangeLog. The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#28) is scheduled for April 22, 2010. A list of the other planned release dates and codenames for 2010 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! [1] http://conferences.yapceurope.org/hack2010dk/
Re: Announcing Rakudo Perl 6 Development release #26 (Amsterdam)
After the command perl Configure.pl --gen-parrot I'm getting the following errors: make -C compilers/pirc clean make[1]: *** No rule to make target `/Users/ivan/Development/rakudo/parrot/config/gen/makefiles/pirc.in', needed by `Makefile'. Stop. and Reading configuration information from parrot_install/bin/parrot_config ... dyld: Library not loaded: /Users/ivan/Development/rakudo/parrot/blib/lib/libparrot.dylib Referenced from: /Users/ivan/Development/rakudo/parrot_install/bin/parrot_config Reason: image not found Died at Configure.pl line 119. I'm running Mac OS X 10.5 on a PowerBook G4. I updated rakudo using git pull. I have already built and uploaded test results twice. So something broke. Ivan.
Announce: Rakudo Perl 6 Development Release #25 (Minneapolis)
[This notice is going out a bit late; the release was indeed produced on time, but I was delayed in sending out this notice. With apologies for the delay... --Pm] On behalf of the Rakudo development team, I'm pleased to announce the January 2010 development release of Rakudo Perl #25 Minneapolis. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine (see http://www.parrot.org). The tarball for the January 2010 release is available from http://github.com/rakudo/rakudo/downloads . Rakudo Perl follows a monthly release cycle, with each release code named after a Perl Mongers group. The January 2010 release is code named Minneapolis for Minneapolis.pm, hosts of the annual Frozen Perl Workshop [1]. In 2009 the Frozen Perl Workshop featured a one-day hackathon for Perl 6 and Rakudo development, which ultimately informed the design and implementation of the current build system. (The 2010 Frozen Perl Workshop will be on February 6, 2010, for those interested in attending.) Shortly after the October 2009 (#22) release, the Rakudo team began a new branch of Rakudo development (ng) that refactors the grammar to much more closely align with STD.pm as well as update some core features that have been difficult to achieve in the master branch [2, 3]. We had planned for this release to be created from the new branch, but holiday vacations and other factors conspired against us. This is absolutely the final release from the old development branch; we expect to make the new branch the official master branch shortly after this release. This release of Rakudo requires Parrot 2.0.0. One must still perform make install in the Rakudo directory before the perl6 executable will run anywhere other than the Rakudo build directory. For the latest information on building and using Rakudo Perl, see the README file section titled Building and invoking Rakudo. Some of the specific changes and improvements occuring with this release include: * Rakudo is now passing 31,957 spectests, or 85.7% of the available test suite. This is roughly the same level as the December 2009 release (because most effort has taken place in the ng branch as described above). * Rakudo's calling conventions have been updated to match changes in Parrot 2.0.0's calling and context structures. The Perl 6 language specification is still in flux. Please take note of the following changes, which might affect your existing programs. In the next release of Rakudo, the deprecated features will likely be gone. * The root of the object hierarchy has been changed from 'Object' to 'Mu'. The type 'Object' goes away. * The term 'undef' is gone. You can replace it with other constructs, depending on context: - 'Nil' is undefined in item context, and the empty list in list context - 'Mu' is the most general undefined value which does not flatten in list context - as a smart matching target, you can replace '$obj ~~ undef' by '$obj ~~ *.notdef' * Builtin classes will derive from 'Cool' (which itself derives from 'Any'). Most of the builtin methods on these classes will be defined in the 'Cool' class instead of 'Any'. See Synopsis 2 for more details. * Starting with the next release, we will likely switch to using .MM instead of -MM (dot instead of hyphen) as release identifiers. This is intended to simplify building and packaging for other distribution systems. The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#26) is scheduled for February 18, 2010. A list of the other planned release dates and codenames for 2010 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! [1] http://www.frozen-perl.org/ [2] http://use.perl.org/~pmichaud/journal/39779 [3] http://use.perl.org/~pmichaud/journal/39874
Announce: Rakudo Perl 6 Development Release #24 (Seoul)
On behalf of the Rakudo development team, I'm pleased to announce the December 2009 development release of Rakudo Perl #24 Seoul. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine (see http://www.parrot.org). The tarball for the December 2009 release is available from http://github.com/rakudo/rakudo/downloads Due to the continued rapid pace of Rakudo development and the frequent addition of new Perl 6 features and bugfixes, we recommend building Rakudo from the latest source, available from the main repository at github. More details are available at http://rakudo.org/how-to-get-rakudo. Rakudo Perl follows a monthly release cycle, with each release code named after a Perl Mongers group. The December 2009 release is code named Seoul for Seoul.pm, who hosted Jonathan so well recently, and because they have a cake duck. Shortly after the October 2009 (#22) release, the Rakudo team began a new branch of Rakudo development (ng) that refactors the grammar to much more closely align with STD.pm as well as update some core features that have been difficult to achieve in the master branch [1, 2]. Most of our effort for the past month has been in this new branch, but as of the release date the new version had not sufficiently progressed to be the release copy. We expect to have the new version in place in the January 2010 release, but may elect to have an interim release from the new branch before then. This release of Rakudo requires Parrot 1.9.0. One must still perform make install in the Rakudo directory before the perl6 executable will run anywhere other than the Rakudo build directory. For the latest information on building and using Rakudo Perl, see the readme file section titled Building and invoking Rakudo. Some of the specific changes and improvements occuring with this release include: * Rakudo is now passing 32,192 spectests, a decrease of 561 passing tests since the November 2009 release. We pass fewer tests now because specification changes caused many obsolete (but passing) tests to be removed from the suite -- from 38,318 in November to 37,376 now. The percentage of passing tests has increased, from 85.5% in November to 86.1% today. * More improvements to the Rat type and related math functions to remain aligned with the specification. The Perl 6 language specification is still in flux. Please take note of the following changes, which might affect your existing programs. In the next release of Rakudo, the deprecated features will likely be gone. * The root of the object hierarchy has been changed from 'Object' to 'Mu'. The type 'Object' goes away. * The term 'undef' is gone. You can replace it with other constructs, depending on context: - 'Nil' is undefined in item context, and the empty list in list context - 'Mu' is the most general undefined value which does not flatten in list context - as a smart matching target, you can replace '$obj ~~ undef' by '$obj ~~ *.notdef' The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#25) is scheduled for January 21, 2010. A list of the other planned release dates and codenames for 2010 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! [1] http://use.perl.org/~pmichaud/journal/39779 [2] http://use.perl.org/~pmichaud/journal/39874
Rakudo Perl 6 development release #23 (Lisbon)
Announce: Rakudo Perl 6 development release #23 (Lisbon) On behalf of the Rakudo development team, I'm pleased to announce the November 2009 development release of Rakudo Perl #23 Lisbon. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine (see http://www.parrot.org). The tarball for the November 2009 release is available from http://github.com/rakudo/rakudo/downloads Due to the continued rapid pace of Rakudo development and the frequent addition of new Perl 6 features and bugfixes, we recommend building Rakudo from the latest source, available from the main repository at github. More details are available at http://rakudo.org/how-to-get-rakudo. Rakudo Perl follows a monthly release cycle, with each release code named after a Perl Mongers group. The November 2009 release is code named Lisbon for Lisbon.pm, who did a marvellous job arranging this year's YAPC::EU. Shortly after the October 2009 (#22) release, the Rakudo team began a new branch of Rakudo development (ng) that refactors the grammar to much more closely align with STD.pm as well as update some core features that have been difficult to achieve in the master branch [1, 2]. Most of our effort for the past month has been in this new branch, but as of the release date the new version had not sufficiently progressed to be the release copy. We expect to have the new version in place in the December 2009 release. This release of Rakudo requires Parrot 1.8.0. One must still perform make install in the Rakudo directory before the perl6 executable will run anywhere other than the Rakudo build directory. For the latest information on building and using Rakudo Perl, see the readme file section titled Building and invoking Rakudo. Some of the specific changes and improvements occuring with this release include: * Rakudo is now passing 32,753 spectests, an increase of 171 passing tests since the October 2009 release. With this release Rakudo is now passing 85.5% of the available spectest suite. * As mentioned above, most development effort for Rakudo in November has taken place in the ng branch, and will likely be reflected in the December 2009 release. * Rakudo now supports unpacking of arrays, hashes and objects in signatures * Rakudo has been updated to use Parrot's new internal calling conventions, resulting in a slight performance increase. The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#24) is scheduled for December 17, 2009. A list of the other planned release dates and codenames for 2009 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! [1] http://use.perl.org/~pmichaud/journal/39779 [2] http://use.perl.org/~pmichaud/journal/39874
Rakudo Perl 6 development release #22 (Thousand Oaks)
Announce: Rakudo Perl 6 development release #22 (Thousand Oaks) On behalf of the Rakudo development team, I'm pleased to announce the October 2009 development release of Rakudo Perl #22 Thousand Oaks. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine (see http://www.parrot.org). The tarball for the October 2009 release is available from http://github.com/rakudo/rakudo/downloads Due to the continued rapid pace of Rakudo development and the frequent addition of new Perl 6 features and bugfixes, we recommend building Rakudo from the latest source, available from the main repository at github. More details are available at http://rakudo.org/how-to-get-rakudo. Rakudo Perl follows a monthly release cycle, with each release code named after a Perl Mongers group. The October 2009 is code named Thousand Oaks for their amazing Perl 6 hackathon, their report at http://www.lowlevelmanager.com/2009/09/perl-6-hackathon.html, and just because I like the name :-) Since the 2009-08 release, Rakudo Perl builds from an installed Parrot instead of using Parrot's build tree. This means that, unlike previous versions of Rakudo Perl, the perl6 (or perl6.exe) executables only work when invoked from the Rakudo root directory until a make install is performed. Running make install will install Rakudo and its libraries into the Parrot installation that was used to build it, and then the executables will work when invoked from any directory. This release of Rakudo requires Parrot 1.7.0. For the latest information on building and using Rakudo Perl, see the readme file section titled Building and invoking Rakudo. (Quick note: the --gen-parrot option still automatically downloads and builds Parrot as before, if you prefer that approach.) Some of the specific changes and improvements occuring with this release include: * Rakudo is now passing 32,582 spectests, an increase of 17,085 passing tests since the September 2009 release. With this release Rakudo is now passing 85.0% of the available spectest suite. * We have a huge increase in the number of spectests relating to the Complex and Rat numeric types. * Complex numbers are now implemented as a Perl 6 class, and supports all trigonometric functions from the specification. * Rakudo has a new signature binder which makes calling routines and operators much faster, and allows binding of positional arguments by name. * Rakudo has improved signature introspection, better errors relating to signatures and signature literals are now supported. * Rakudo now supports accessing outer lexical variables from classes and packages. * Some new variants of the series operator are now implemented. * When configuring Rakudo with --gen-parrot, the --optimize flag is now passed to Parrot's Configure.pl The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#23) is scheduled for November 19, 2009. A list of the other planned release dates and codenames for 2009 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! -Scott -- Jonathan Scott Duff perlpi...@gmail.com
Announce: Rakudo Perl 6 development release #21 (Seattle)
On behalf of the Rakudo development team, I'm pleased to announce the September 2009 development release of Rakudo Perl #21 Seattle. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine [1]. The tarball for the September 2009 release is available from http://github.com/rakudo/rakudo/downloads . Due to the continued rapid pace of Rakudo development and the frequent addition of new Perl 6 features and bugfixes, we recommend building Rakudo from the latest source, available from the main repository at github. More details are available at http://rakudo.org/how-to-get-rakudo. Rakudo Perl follows a monthly release cycle, with each release code named after a Perl Mongers group. September 2009 is code named Seattle for the enthusiasm they have shown for Perl 6 during monthly meetings, and the feedback, encouragement and support given me for the past several years. Since the 2009-08 release, Rakudo Perl builds from an installed Parrot instead of using Parrot's build tree. This release of Rakudo requires Parrot 1.6.0. For the latest information on building and using Rakudo Perl, see the README file section titled Building and invoking Rakudo. (Quick note: the --gen-parrot option still automatically downloads and builds Parrot as before, if you prefer that approach.) Also, unlike previous versions of Rakudo Perl, the perl6 (or perl6.exe) executables only work when invoked from the Rakudo root directory until a make install is performed. Running make install will install Rakudo and its libraries into the Parrot installation that was used to build it, and then the executables will work when invoked from any directory. Some of the specific major changes and improvements occuring with this release include: * Rakudo is now passing 15,497 spectests, an increase of 3,128 passing tests since the August 2009 release. With this release Rakudo is now passing 71.5% of the available spectest suite. * Rakudo now supports contextual variables. * Rakudo now supports the rational (Rat) data type. * Rakudo now supports overloading of many of the builtin operators, many of which are now defined in the core setting. Many have also been improved to be more faithful to the specification with respect to types and coercions. * Substantially improved support for trait handling. Most of the built-in traits are now defined in the core setting. * The %*ENV variable now works properly for modifying the process environment. Since the Perl 6 specification is still in flux, some deprecated features have been removed from Rakudo. Prominently among those are: * '=$handle' is deprecated in favor of '$handle.get' (one line) and '$handle.lines' (all lines). * 'int $obj' is deprecated in favor of '$obj.Int'. The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#22) is scheduled for October 22, 2009. A list of the other planned release dates and codenames for 2009 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! References: [1] Parrot, http://parrot.org/
Announce: Rakudo Perl 6 development release #20 (PDX)
On behalf of the Rakudo development team, I'm pleased to announce the August 2009 development release of Rakudo Perl #20 PDX. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine [1]. The tarball for the August 2009 release is available from http://github.com/rakudo/rakudo/downloads . Due to the continued rapid pace of Rakudo development and the frequent addition of new Perl 6 features and bugfixes, we continue to recommend that people wanting to use or work with Rakudo obtain the latest source directly from the main repository at github. More details are available at http://rakudo.org/how-to-get-rakudo . Rakudo Perl follows a monthly release cycle, with each release code named after a Perl Mongers group. August 2009 is code named PDX for the Portland Perl Mongers. PDX.pm has been home to several Rakudo contributors (chromatic, Allison Randal, and more) and PDX.pm has held meetings that have produced feature and bugfix patches for Rakudo. Beginning with this release, Rakudo Perl builds from an installed Parrot instead of using Parrot's build tree. This release of Rakudo requires Parrot 1.5.0. For the latest information on building and using Rakudo Perl, see the README file section titled Building and invoking Rakudo. (Quick note: the --gen-parrot option still automatically downloads and builds Parrot as before, if you prefer that approach.) Also, unlike previous versions of Rakudo Perl, the perl6 (or perl6.exe) executables only work when invoked from the Rakudo root directory until a make install is performed. Running make install will install Rakudo and its libraries into the Parrot installation that was used to build it, and then the executables will work when invoked from any directory. Some of the specific major changes and improvements occuring with this release include: * Rakudo is now passing 12,369 spectests, an increase of 493 passing tests since the July 2009 release. With this release Rakudo is now passing 69.98% of the available spectest suite. * We now have a much cleaner traits implementation. Many of the Perl 6 built-in traits are now implemented in Perl 6, and user-defined traits can now be defined and applied to classes and roles. * The 'hides' trait on classes can make one class hide another. * Many not-yet-implemented operators and features now provide more helpful error messages instead of simply producing parse errors. * The ROADMAP has been substantially updated and includes some details regarding the Rakudo Star release [2]. * Embedded comments now require backticks (Perl 6 specification change). Since the Perl 6 specification is still in flux, some deprecated features will be removed from Rakudo. Prominently among those are: * '=$handle' is deprecated in favor of '$handle.get' (one line) and '$handle.lines' (all lines). * 'int $obj' is deprecated in favor of '$obj.Int'. The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#21) is scheduled for September 17, 2009. A list of the other planned release dates and codenames for 2009 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! References: [1] Parrot, http://parrot.org/ [2] Rakudo Star, http://use.perl.org/~pmichaud/journal/39411
Rakudo Perl 6 development release #18 (Pittsburgh)
On behalf of the Rakudo development team, I'm pleased to announce the June 2009 development release of Rakudo Perl #18 Pittsburgh. Rakudo is an implementation of Perl 6 on the Parrot Virtual Machine [1]. The tarball for the June 2009 release is available from http://github.com/rakudo/rakudo/downloads . Due to the continued rapid pace of Rakudo development and the frequent addition of new Perl 6 features and bugfixes, we continue to recommend that people wanting to use or work with Rakudo obtain the latest source directly from the main repository at github. More details are available at http://rakudo.org/how-to-get-rakudo . Rakudo Perl follows a monthly release cycle, with each release code named after a Perl Mongers group. This release is named Pittsburgh, which is the host for YAPC|10 (YAPC::NA 2009) [2] and the Parrot Virtual Machine Workshop [3]. Pittsburgh.pm has also sponsored hackathons for Rakudo Perl as part of the 2008 Pittsburgh Perl Workshop [4]. In this release of Rakudo Perl, we've focused our efforts on refactoring many of Rakudo's internals; these refactors improve performance, bring us closer to the Perl 6 specification, operate more cleanly with Parrot, and provide a stronger foundation for features to be implemented in the near future. Some of the specific major changes and improvements in this release include: * Rakudo is now passing 11,536 spectests, an increase of 194 passing tests since the May 2009 release. With this release Rakudo is now passing 68% of the available spectest suite. * Method dispatch has been substantially refactored; the new dispatcher is significantly faster and follows the Perl 6 specification more closely. * Object initialization via the BUILD and CREATE (sub)methods is substantially improved. * All return values are now type checked (previously only explicit 'return' statements would perform type checking). * String handling is significantly improved: fewer Unicode-related bugs exist, and parsing speed is greatly improved for some programs containing characters in the Latin-1 set. * The IO .lines and .get methods now follow the specification more closely. * User-defined operators now also receive some of their associated meta variants. * The 'is export' trait has been improved; more builtin functions and methods can be written in Perl 6 instead of PIR. * Many Parrot changes have improved performance and reduced overall memory leaks (although there's still much more improvement needed). The development team thanks all of our contributors and sponsors for making Rakudo Perl possible. If you would like to contribute, see http://rakudo.org/how-to-help , ask on the perl6-compi...@perl.org mailing list, or ask on IRC #perl6 on freenode. The next release of Rakudo (#19) is scheduled for July 23, 2009. A list of the other planned release dates and codenames for 2009 is available in the docs/release_guide.pod file. In general, Rakudo development releases are scheduled to occur two days after each Parrot monthly release. Parrot releases the third Tuesday of each month. Have fun! References: [1] Parrot, http://parrot.org/ [2] YAPC|10 http://yapc10.org/yn2009/ [3] Parrot Virtual Machine Workshop, http://yapc10.org/yn2009/talk/2045 [4] Pittsburgh Perl Workshop, http://pghpw.org/ppw2008/
Re: Rakudo Perl 6 development release #17 (Stockholm)
On Thu, 28 May 2009 22:58:47 +0100, Nelo Onyiah nelo.ony...@googlemail.com wrote: That appears to have fixed it. Here are the results of the spectess: Test Summary Report --- t/spec/S02-literals/quoting.rakudo (Wstat: 0 Tests: 136 Failed: 0) TODO passed: 24 t/spec/S09-subscript_slice/slice.rakudo (Wstat: 10 Tests: 27 Failed: 0) Non-zero wait status: 10 Files=383, Tests=11494, 981 wallclock secs ( 6.79 usr 3.52 sys + 1679.86 cusr 95.69 csys = 1785.86 CPU) Result: FAIL I've confirmed that ``parrot_config --dump'' doesn't die w/o --optimize option in the configuration using the HEAD's source. Thanks, -- Hiroyuki Hanai ha...@s2factory.co.jp S2 Factory, Inc. http://www.s2factory.co.jp/ Tokyo, JAPAN
