> I think it is best if you open an issue for this, so that it will not fall
> through the cracks.
Okay, fair enough:
https://github.com/rakudo/rakudo/issues/4245
On 3/7/21, Elizabeth Mattijsen wrote:
>> On 7 Mar 2021, at 00:16, Joseph Brenner wrote:
>>
>> Is there anything like an equivalent
> On 7 Mar 2021, at 00:16, Joseph Brenner wrote:
>
> Is there anything like an equivalent of "man perlguts" for Raku/rakudo?
>
> There are things like this, but they seem to be very out-of-date:
>
> https://github.com/rakudo/rakudo/blob/master/docs/architecture.html
That is indeed severely ou
hello,
On Tue, Jul 09, 2019 at 11:28:29PM +0200, Laurent Rosenfeld via perl6-users
wrote:
> I have updated the Wikipedia page linked in Marc's message. @Marc: please
> check it and let me know if you see any remaining issues.
reading the fix, i realized i mixed up the errors of the linuxfr page
I have updated the Wikipedia page linked in Marc's message. @Marc: please
check it and let me know if you see any remaining issues.
@JJMerelo: I have devoted a lot of efforts translating various P6
documentation into French over the last 5 years or so, including
perl6intro, and probably 250 to 300
hello,
> There have been some efforts to translate perl6intro; but as Laurent says,
> we can hardly say the documentation is complete, so diverting resources to
> translation is probably not such a good idea.
yeah. when laurent spoke about a moving target, i gave a look at the doc
repo and there
hello Laurent,
> the French Wikipedia page you refer to is not really wrong, but rather
> terribly outdated and, therefore, no longer correct. I have a Wikipedia
> account and can easily fix that page (using, if needed, the updated English
> Wikipedia page on the same subject).
The very first sen
There have been some efforts to translate perl6intro; but as Laurent says,
we can hardly say the documentation is complete, so diverting resources to
translation is probably not such a good idea.
El mar., 9 jul. 2019 a las 21:53, Laurent Rosenfeld via perl6-users (<
perl6-us...@perl.org>) escribió
Hi Marc,
the French Wikipedia page you refer to is not really wrong, but rather
terribly outdated and, therefore, no longer correct. I have a Wikipedia
account and can easily fix that page (using, if needed, the updated English
Wikipedia page on the same subject).
Translating the whole Perl 6/Rak
On Mon, 24 Oct 2016, Parrot Raiser wrote:
Where's the best current description of error messages from file
"open" commands, and how to control them?
`git grep 'does X::IO'` is your best bet right now because some
X::IO-exceptions are not documented yet.
On 6/22/07, Smylers wrote:
David Green writes:
Well, clutter like "Blah: none" seems to me to be more the fault of
the doc-formatter for not hiding lines like that.
It's more the repetition in the lines you snipped that I really object to:
Ah. (That was sneaky of me.) I agree with that --
David Green writes:
> Well, clutter like "Blah: none" seems to me to be more the fault of
> the doc-formatter for not hiding lines like that.
It's more the repetition in the lines you snipped that I really object
to: given the function's name, the name(s) of its parameter(s), and the
short descri
On 6/21/07, Smylers wrote:
Mark Overmeer writes:
> The boundary between freedom and anacharchy is faint.
Indeed. And I'd much rather we err on the side of anarchy.
I'd much rather we didn't err at all! Just because something isn't
"perfect" doesn't mean it's an error, or that it's not worth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 19, 2005, at 10:15 AM, Kevin Tew wrote:
I've been watching pugs for a while and would like to get more
involved.
To that end I've been exploring the source tree.
As a newbie, I've got a lot of questions, So I'm attempting to
learn by
On Fri, 2005-08-19 at 09:15 -0600, Kevin Tew wrote:
> Anyway, this is my first attempt at a pugs doc patch :)
> Comments welcome!
Welcome. I'm sure someone will offer you a commit bit very soon. In
the meantime, my only comment is that, outside of class, module, file,
and package names, where s
On Sat, Jul 02, 2005 at 10:17:01AM -0600, John Williams wrote:
: There is something to be said for actually _organizing_ the documentation
: too, which is why POD docs for a function are not always next to the
: function itself.
I always cringe when I hear "the documentation", as if it's only one
On Thu, 30 Jun 2005, chromatic wrote:
> On Thu, 2005-06-30 at 04:33 +, David Formosa (aka ? the Platypus)
> wrote:
> > I'm just wondering if a documentation trait on subs would be usefull.
> > If we are going to have something like p6explain the doc trait could
> > be used as the source for the
On Thu, 2005-06-30 at 04:33 +, David Formosa (aka ? the Platypus)
wrote:
> I'm just wondering if a documentation trait on subs would be usefull.
> If we are going to have something like p6explain the doc trait could
> be used as the source for the infomation for it. p6explain would
> simply h
17 matches
Mail list logo
