Branch: refs/heads/master
Home: https://github.com/perl6/specs
Commit: be783f75c4a0e58ce5588e304f8163cb32fca8e8
https://github.com/perl6/specs/commit/be783f75c4a0e58ce5588e304f8163cb32fca8e8
Author: Tom Browder
Date: 2016-07-11 (Mon, 11 Jul 2016)
Changed paths:
M S26-do
On Tue, Jul 12, 2016 at 08:48:59AM -0500, Tom Browder wrote:
> > If --help mentions a man page, it's probably sufficient to ship Rakudo
> > with an already-translated man page, rather than shipping the translator.
>
>Very true--the voice of reason!
>
>But shouldn't all the pod6-to-X trans
On Tuesday, July 12, 2016, Patrick R. Michaud wrote:
> I think any pod2man translator program should be separate from Rakudo
> itself.
>
> If --help mentions a man page, it's probably sufficient to ship Rakudo
> with an already-translated man page, rather than shipping the translator.
Very true
I think any pod2man translator program should be separate from Rakudo itself.
If --help mentions a man page, it's probably sufficient to ship Rakudo
with an already-translated man page, rather than shipping the translator.
Pm
On Tue, Jul 12, 2016 at 04:34:00AM -0500, Tom Browder wrote:
>On M
# New Ticket Created by Wenzel Peppmeyer
# Please include the string: [perl #128610]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128610 >
constant B::b = 666;
# OUTPUTĀ«===SORRY!=== Error while compiling ā¤Missing initializer
On Monday, July 11, 2016, Will Coleda via RT > wrote:
> On Sat Jul 09 13:51:07 2016, tbrowder wrote:
> > Need a pod2man translator.
> Does this need to be shipped with the rakudo compiler?
Since the perl6 program --help once mentioned the perl6 man page, maybe it
should.
-Tom
