use Test;
plan 8;
my $p = 0;
my $r;
=begin pod =for DESCRIPTION :title = :authorBrown> :pubdate(2011) =end pod $r = $=pod[$p++].contents[0];
is $r.config, 'presentation template';
is $r.config, 'John Brown';
is $r.config, 2011;
=begin pod =for head1 :attr('key&
On Sun, Jan 2, 2022 at 8:00 PM Richard Hainsworth
wrote:
>
> What does not work (in that 'newkey' is not found in the 'config' part
> of the Pod::Block returned by $=pod
>
> =head1 :key
>
> = :newkey
I just tried that with Rakudo v2031.03 and got a com
has not been implemented.
This is wrong in some way, either the implementation is incorrect, or
the documentation is incorrect. But config data CAN be supplied on
succeeding lines.
What does not work (in that 'newkey' is not found in the 'config' part
of the Pod::Block r
the other questions?
>
Regarding the other questions:
1. I believe there are no reserved words for the '=begin/=end comment'.
However, nested comments I believe were an issue at one time but they
aren't now.
3. That depends on what you're doing. For example, currently the
On Mon, Jul 19, 2021 at 06:57 Marcel Timmerman wrote:
Reading a bit, I came across old documents (with a warning that these are
> out of date) https://design.raku.org/S02.html#Multiline_Comments . It
> states that any unrecognized format name should be treated as a comment
> block, which the abov
can find the test code when I process the pod data. The tag added to
begin will not pose a problem. I need the code section to keep the
newlines in. The problem now is when one needs to render other pod data
to html or markdown, this part comes with it like shown the next
markdown output
Thank you for answer JJ.
It is quite a work to split such a large file up so I thought I'd better
ask before I dive in head first. Later I might think it over. I have
this documentation on the github pages too so I could separate the pod
doc and keep them somewhere else where they won&
s 14:20, Marcel Timmerman ()
escribió:
> Hi,
>
> I was wondering if pod documentation has a large impact on compiling
> modules. I assume on small files it would be ignorable but I have some
> modules which have grown big, one has 7153 lines of which the biggest
> part is pod doc. W
Hi,
I was wondering if pod documentation has a large impact on compiling
modules. I assume on small files it would be ignorable but I have some
modules which have grown big, one has 7153 lines of which the biggest
part is pod doc. Would it be useful to split such a file in two. one for
code
On 2020-05-30 21:28, Kevin Pye wrote:
While the original documentation you were referring to called them Pod
comments, that's not really accurate. The full documentation (to which I
referred you) calls them "Pod documents" which is much more descriptive.
The Pod document is p
While the original documentation you were referring to called them Pod
comments, that's not really accurate. The full documentation (to which I
referred you) calls them "Pod documents" which is much more descriptive.
The Pod document is parsed by Rakudo, and the contents can be used
t;> wrote:
>>
>> Hi All,
>>
>> I am somewhat confused about pod comments:
>>
>> https://docs.raku.org/language/syntax#Pod_comments
>>
>> Seems pretty straight forward. But when I look at
>
>>
> >> Hi All,
> >>
> >> I am somewhat confused about pod comments:
> >>
> >> https://docs.raku.org/language/syntax#Pod_comments
> >>
> >> Seems pretty straight forward. But when I look at
> >>
&
On Sun, 31 May 2020 at 12:43, ToddAndMargo via perl6-users
mailto:perl6-us...@perl.org>> wrote:
Hi All,
I am somewhat confused about pod comments:
https://docs.raku.org/language/syntax#Pod_comments
Seems pretty straight forward. But when I look at
https://gith
They're not Pod comments, they're Pod abbreviated blocks:
https://docs.raku.org/language/pod
Kevin.
On Sun, 31 May 2020 at 12:43, ToddAndMargo via perl6-users <
perl6-us...@perl.org> wrote:
> Hi All,
>
> I am somewhat confused about pod comments:
>
> https:
Hi All,
I am somewhat confused about pod comments:
https://docs.raku.org/language/syntax#Pod_comments
Seems pretty straight forward. But when I look at
https://github.com/tadzik/perl6-Config-INI/blob/master/lib/Config/INI.pm
starting line 45, I see
=begin pod
=head1 NAME
=head1 SYNOPSIS
> Wouldn't it be useful if Vadim commented on an appropriate GH issue?
> If so, which would that be?
> https://github.com/perl6/user-experience/issues/35
> <https://github.com/perl6/user-experience/issues/35> ?
> https://github.com/perl6/Pod-To-HTML/issues/55
> <
Hi JJ,
Wouldn't it be useful if Vadim commented on an appropriate GH issue?
If so, which would that be?
https://github.com/perl6/user-experience/issues/35 ?
https://github.com/perl6/Pod-To-HTML/issues/55 ?
https://github.com/perl6/doc/issues/167 ?
Somewhere else?
--
raiph
On Mon, Jan 14, 20
It can be used to define where the links
> must point to. Something like:
>
> =config github:/user/module/tree/master/docs
>
> I'm not sure =config is implemented right now, my money is on NYI. And still
> there's the problem that pod6 or pod-embedded-in-Perl6 is not rend
; directive. It can be used to define where the links must point to.
> Something like:
>
> =config github:/user/module/tree/master/docs
>
I'm not sure =config is implemented right now, my money is on NYI. And
still there's the problem that pod6 or pod-embedded-in-Perl6 is not
re
some in gitlab...
>
> Any suggestion is welcome, meanwhile.
>
> El sáb., 12 ene. 2019 a las 2:22, Vadim Belman ( <mailto:vr...@lflat.org>>) escribió:
> Hello,
>
> How do I properly write a link to a module in a POD documentation? Actually,
> the question
nk to a module in a POD documentation?
> Actually, the question is even more complex as it might be both a module
> and a .pod.
>
> The documentation (https://docs.perl6.org/language/pod) isn't clear on
> this subject. When it comes to `L<>` docs are mostly focused on URL
Hello,
How do I properly write a link to a module in a POD documentation? Actually,
the question is even more complex as it might be both a module and a .pod.
The documentation (https://docs.perl6.org/language/pod) isn't clear on this
subject. When it comes to `L<>` docs are mostly
On Tue, Oct 16, 2018 at 10:11 JJ Merelo > wrote:
> Thanks for your answer, Tom.
>
You’re, welcome, JJ!
-Tom
Thanks for your answer, Tom.
El mar., 16 oct. 2018 a las 16:39, Tom Browder ()
escribió:
> On Tue, Oct 16, 2018 at 08:55 Richard Hainsworth
> wrote:
>
>> Tom
>> I was trying not to bother you with all my questions 😁
>>
>
> Never a bother, Richard!
>
> How
On Tue, Oct 16, 2018 at 08:55 Richard Hainsworth
wrote:
> Tom
> I was trying not to bother you with all my questions 😁
>
Never a bother, Richard!
However I looked at all the classes of pod and they sub class block. So
> which do not
>
Pod::Config and Pod::Raw
I’ve not yet lo
On Tue, Oct 16, 2018 at 00:31 Richard Hainsworth
wrote:
> In the type documentation for POD under Pod::Block it states:
>
> "Class for a Pod block, and base class for most other Pod classes."
The pod classes that currently exist are in Rakudo repo
rakudo/src/core/Pod.pm6. Na
In the type documentation for POD under Pod::Block it states:
"Class for a Pod block, and base class for most other Pod classes."
'most' means inter alia 'not all'. So this statement is saying that
there are *other* Pod classes which are not Pod::Block.
I
closed also with tests in merged roast PR #371
closed also with tests in merged roast PR #371
closed also with tests in merged roast PR #371
closed also with tests in merged roast PR #371
closed by merge of rakudo PR #1339
closed by merge of rakudo PR #1339
closed by merge of rakudo PR #1339
closed by merge of rakudo PR #1339
# New Ticket Created by Tom Browder
# Please include the string: [perl #132650]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132650 >
Given this nqp code:
=begin comment
some code
...
=begin comment
some
# New Ticket Created by Tom Browder
# Please include the string: [perl #132632]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132632 >
The following pod configuration value formats are NYI:
Type Exam
, autarch wrote:
> Given this code:
>
> =begin pod
>
> =begin table :caption('My caption')
>
> Title | Name | Size
> ==
> Captain | Jane | Medium
> Clerk | Bob | Large
>
> =end table
>
> =end pod
>
> dd $=pod[0];
>
On Sat, 26 Dec 2015 14:27:04 -0800, autarch wrote:
> There's a class in rakudo's Pod.pm named Pod::Raw, but rakudo does not
> produce these blocks. I'm not sure whether the bug is that the class
> exists or that it's never used.
I *think* it's meant to be Pod::B
Still reproducible (2017.11,HEAD(e5b660e))
On 2015-05-07 04:43:49, FROGGS.de wrote:
> =begin DATAfoo=end DATAsay $=pod
> rakudo-moar 89c43c: OUTPUT«postcircumfix:<{ }> not defined for type
> Array in block at /tmp/xaDmKlMgSo:4»
>
> See also: https://github.com/perl6/
tests added in roast PR #353
tests added in roast PR #353
tests added in roast PR #353
tests added in roast PR #353
Root problem is fixed by PR #1240.
Fixed by PR #1240.
Fixed by PR #1240.
Fixed by PR #1240.
Fixed by PR #1240.
Probably one of a number of things that would be easy if we made pod
another language on the braid :)
On Mon, Nov 27, 2017 at 11:59 AM Timo Paulssen via RT <
perl6-bugs-follo...@perl.org> wrote:
> a look at a profile makes me suspect the problem is having
> pod_string_character ma
Probably one of a number of things that would be easy if we made pod
another language on the braid :)
On Mon, Nov 27, 2017 at 11:59 AM Timo Paulssen via RT <
perl6-bugs-follo...@perl.org> wrote:
> a look at a profile makes me suspect the problem is having
> pod_string_character ma
a look at a profile makes me suspect the problem is having pod_string_character
match a single character at a time, causing rather large numbers of match
objects for comparatively short strings.
It's probably worthwhile to steal a piece of implementation from "nibbling",
aka parsing strings. a
On Mon, 30 Oct 2017 09:16:23 -0700, tbrowder wrote:
> On Mon, 30 Oct 2017 08:21:04 -0700, tbrowder wrote:
> > On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote:
> >
> > > A —ll-exception stacktrace would be useful in such a case :-)
> >
> >
> > WILCO!
$ cat prob.p6
use v6;
# an empty ta
On Mon, 30 Oct 2017 08:21:04 -0700, tbrowder wrote:
> On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote:
>
> > A —ll-exception stacktrace would be useful in such a case :-)
>
>
> WILCO!
Expected "=end comment" to terminate "=begin comment"; found "=end table" instead.
at SETTING::s
On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote:
> A —ll-exception stacktrace would be useful in such a case :-)
WILCO!
On Mon, Oct 30, 2017 at 09:53 Elizabeth Mattijsen wrote:
> A —ll-exception stacktrace would be useful in such a case :-)
WILCO!
issue.
> # https://rt.perl.org/Ticket/Display.html?id=132377 >
>
>
> The following pod causes an exception
>
> =begin comment
> =begin table
> a | b | c
> =end table
> =end comment
>
> If the =begin/=end table lines are indented by one space the exception is
> not thrown
issue.
> # https://rt.perl.org/Ticket/Display.html?id=132377 >
>
>
> The following pod causes an exception
>
> =begin comment
> =begin table
> a | b | c
> =end table
> =end comment
>
> If the =begin/=end table lines are indented by one space the exception is
> not thrown
# New Ticket Created by Tom Browder
# Please include the string: [perl #132377]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132377 >
The following pod causes an exception
=begin comment
=begin table
a | b | c
=end ta
# New Ticket Created by Tom Browder
# Please include the string: [perl #132348]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132348 >
The following table causes an exception:
=begin table
some cells Z
=end table
And also:
https://github.com/tadzik/perl6-Acme-Meow/blob/35286b14447d22516fbf68767c4d7e18b7396971/lib/Acme/Meow.pm#L65-L69
https://github.com/skids/perl6-Control-Bail/blob/3e6ab6c3bab9176a44476bd0883ba99205306400/lib/Control/Bail.pm6#L81
https://github.com/tadzik/Grammar-BNF/blob/14f51ca5882f00f0ac
Just for the record, there was another module affected by this:
https://github.com/nkh/P6-Text-Template/blob/5e1752c08ddb064e366be862fd500c4de0c4b833/lib/Text/Template.pm#L142
On 2017-10-21 10:44:51, c...@zoffix.com wrote:
> On Sat, 21 Oct 2017 09:06:24 -0700, alex.jakime...@gmail.com wrote:
> > C
# New Ticket Created by Tom Browder
# Please include the string: [perl #132341]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132341 >
Consider the following pod 6 tables:
=begin table
a | b | c
m | n | o
x | y
=end ta
On Sat, 21 Oct 2017 09:06:24 -0700, alex.jakime...@gmail.com wrote:
> Code:
> =SEE-ALSO foo
>
>
> ¦«2017.09,963a0f0657^»:
>
>
> ¦«963a0f0,HEAD(312cac7)»:
> ===SORRY!=== Error while compiling /tmp/8cNEnQJfmq
> Preceding context expects a term, but found infix = instead
> at /tmp/8cNEnQJfmq:1
> -
On Sat, 21 Oct 2017 09:06:24 -0700, alex.jakime...@gmail.com wrote:
> Code:
> =SEE-ALSO foo
>
>
> ¦«2017.09,963a0f0657^»:
>
>
> ¦«963a0f0,HEAD(312cac7)»:
> ===SORRY!=== Error while compiling /tmp/8cNEnQJfmq
> Preceding context expects a term, but found infix = instead
> at /tmp/8cNEnQJfmq:1
> -
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132339]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132339 >
Code:
=SEE-ALSO foo
¦«2017.09,963a0f0657^»:
¦«963a0f0,HEAD(312cac
v6d.pod
Log Message:
---
Try to fix pod
v6d.pod
Log Message:
---
Fix POD error
ing and not parse it, while it should just parse the
POD formatting code.
eg.
#| this is I
sub test(){};
say $=pod[0].leading;
will result in
"this is I"
instead of "this is fine" or ["this is",
Pod::FormattingCode{:type("C")}] or wh
On 03/01/2017 03:50 PM, Will Coleda wrote:
Not true, '=for' is part of POD6. See below.
If you're getting errors, it's helpful to reduce the example to a
reasonably small bit of code that duplicates the same error; either
you'll realize the issue as you remove unrelated bits of code, or
you'll e
Not true, '=for' is part of POD6. See below.
If you're getting errors, it's helpful to reduce the example to a
reasonably small bit of code that duplicates the same error; either
you'll realize the issue as you remove unrelated bits of code, or
you'll end up with an example that epitomizes the pro
Hi,
Is it true that the '=for' is taken out of the pod language? I get
errors when I use it. It should take the line and the next lines as a
block. I've also seen that it has the same effect now when I don't use it.
Regards,
Marcel
The rest
all parse OK but the rest simply stringify whatever is inside the `()`:
=begin table :foo('meow') :bar :ber(Q|foos|) :var(join "\n", )
The Bowler Carol PinnslerHaunted bowling ball
=end table
dd $=pod
# [Pod::Block::Table.new(
# New Ticket Created by Will Coleda
# Please include the string: [perl #129925]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129925 >
=begin pod
BadN.
=end pod
renders as:
Badthings are happening.
While not spec
On Thu, Oct 13, 2016 at 8:32 PM, Zoffix Znet via RT
wrote:
>
> PR merged[^1]; tests needed.
>
> [1]
> https://github.com/rakudo/rakudo/commit/7af9ec9d90d4ec8e9732e979729df85a80f7ec11
See perl/roast PR 168.
string: [perl #129862]
> > > # in the subject line of all future correspondence about this
> > > issue.
> > > # https://rt.perl.org/Ticket/Display.html?id=129862 >
> > >
> > >
> > > Consider pod.pl:
> > >
> > > =begin p
gt;
> Consider pod.pl:
>
> =begin pod
>
> =begin table
> a | b | c
> l | m | n
> x | y
> =end table
With the current state of rakudo
pod
, ill-formed tables are problematic. Try redoing the table like this
(adding the separator for the missing column, making the column s
# New Ticket Created by David Warring
# Please include the string: [perl #129862]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129862 >
Consider pod.pl:
=begin pod
=begin table
a | b | c
l | m | n
x | y
=end table
=
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
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
On Sat Jul 09 13:51:07 2016, tbrowder wrote:
> Need a pod2man translator.
Does this need to be shipped with the rakudo compiler?
--
Will "Coke" Coleda
# New Ticket Created by Tom Browder
# Please include the string: [perl #128587]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128587 >
Need a pod2man translator.
# New Ticket Created by Tom Browder
# Please include the string: [perl #128570]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128570 >
>From irc #perl6 2016-07-06:
[21:35] tbrowder: also right now there is no way to set/res
# New Ticket Created by Tom Browder
# Please include the string: [perl #128569]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128569 >
>From irc #perl5, 2016-07-06:
[21:28] tbrowder: if you are working on Pod::*
I am working on this issue and would like ownership of it.
On Wed, Jun 29, 2016 at 9:00 AM, Will Coleda wrote:
> On Tue, Jun 28, 2016 at 5:32 PM, Tom Browder wrote:
>> I am trying to debug a P6 pod problem, and the problem code seems to be in
>> file:
>>
>> rakudo/src/Perl6/Pod.nqp
>>
>> My question is how can
On Tue, Jun 28, 2016 at 5:32 PM, Tom Browder wrote:
> I am trying to debug a P6 pod problem, and the problem code seems to be in
> file:
>
> rakudo/src/Perl6/Pod.nqp
>
> My question is how can I access code in that file?
>
> + Can I write an nqp script, use the Perl6:
I am trying to debug a P6 pod problem, and the problem code seems to be in file:
rakudo/src/Perl6/Pod.nqp
My question is how can I access code in that file?
+ Can I write an nqp script, use the Perl6::Pod module, and operate that way?
+ How do I feed a chunk of pod to the routines?
Any help
# New Ticket Created by Tom Browder
# Please include the string: [perl #128498]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128498 >
According to S26, headings may be numbered in nested format:
Alternatively, as a short-ha
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #128221]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128221 >
continuing my problems with p6 pod: I have scrubbed a bad
pod file down
wrote:
> Hello!
>
> Add, please, semantic block "=EXAMPLES" to pod.
> http://design.perl6.org/S26.html#Semantic_blocks
>
> Examples are very often missing in classical man pages.
>
> Thank you,
> Hans
>
On 16/05/16 14:00, Hans Ginzel wrote:
Hello!
Add, please, semantic block "=EXAMPLES" to pod.
http://design.perl6.org/S26.html#Semantic_blocks
Examples are very often missing in classical man pages.
Thank you,
Hans
Hello Hans,
it says in the speculations that all uppercase block
Hello!
Add, please, semantic block "=EXAMPLES" to pod.
http://design.perl6.org/S26.html#Semantic_blocks
Examples are very often missing in classical man pages.
Thank you,
Hans
On Sunday, May 15, 2016, mt1957 wrote:
>
> Pod::To::PDF
>> ==
>>
>> Nice to have. It could use something like p6pod2latex as an
>> intermediate filter and then use popular LaTeX tools to generate the PDF.
>
> At the moment I am writing pod6 in separa
Hi Tom,
Pod::To::PDF
==
Nice to have. It could use something like p6pod2latex as an
intermediate filter and then use popular LaTeX tools to generate the PDF.
At the moment I am writing pod6 in separate files with the following at
the top of such a file. It needs wkhtmltopdf for this
I am enjoying the Perl 6 community and contributing tidbits to the docs.
In working with the docs, in Pod 6, I think I see some worthwhile Perl 6
Pod projects that interest me, and I would appreciate any comments. (Note
that the new program and module names are kind of lame and definitely need
On 04/25/2016 03:27 PM, Tadeusz Sośnierz wrote:
On 25/04/16 14:13, Tom Browder wrote:
I would like to hack on the pod handling code (particularly the HTML
generation) but it seems to be quite scattered around github. Is
http://github.com/perl6/Pod::To::HTML>> the definitive repo locati
1 - 100 of 555 matches
Mail list logo
