Re: Re: Re: Wanted: Perl 6 Programmers

Well, you mentioned "there should be enough to get you started in languages/perl6/overview.pod" in the post, so I was thinking of that one. That is, let us read it without downloading/installing the whole thing.

If Perl6 stuff is already on perl.org or here in the documentation section, how about a link to it? The implication was that this leading-edge stuff would superceed any of that, since you mentioned mailing lists for discussion but no documents other than overview.pod.

Comment on Re: Re: Re: Wanted: Perl 6 Programmers Download Code

Replies are listed 'Best First'.
Re: Re: Re: Re: Wanted: Perl 6 Programmers by mdillon (Priest) on Sep 05, 2002 at 21:26 UTC
The Parrot docs can be found, converted from POD to HTML, on the Parrot website. In particular, overview.pod can be found here. I believe that they are regularly and automatically updated from the Parrot CVS repository.	[reply]
Re: Wanted: Perl 6 Programmers by sfink (Deacon) on Sep 05, 2002 at 22:25 UTC
Actually, I think he was referring to languages/perl6/overview.pod, which isn't picked up by the automatic POD to HTML converter. There is also a lot of POD buried in source files that would be nice to have on the website, too.	[reply]
Re: Re: Re: Re: Wanted: Perl 6 Programmers by Anonymous Monk on Sep 05, 2002 at 21:30 UTC
Heh. "Started" in this case means "started hacking on the compiler". `overview.pod` is a roadmap of the compiler code, not a document about what is and is not implemented, how to use it, etc. In the past, the "user volume" has been small enough that "read the code" or "look at the examples" has been the "documentation" for what is and isn't implemented. There should probably be a list of what does and does not work somewhere. As for the language itself, here are links to the apocalypses and exegeses, which reflect almost all knowledge of Perl 6 outside Damian's and Larry's heads. If you try to run many of the programs and snippets therein, they will break, hopefully with an informative error message (like "parse error in the following statement"), informing you that those parts of the language are not yet implemented. /s	[reply] [d/l]