Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

parsing does not create raw blocks #4939

Open
p6rt opened this issue Dec 26, 2015 · 3 comments
Open

parsing does not create raw blocks #4939

p6rt opened this issue Dec 26, 2015 · 3 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Dec 26, 2015

Migrated from rt.perl.org#127038 (status was 'open')

Searchable as RT127038$

@p6rt
Copy link
Author

p6rt commented Dec 26, 2015

From @autarch

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 note that for something like "=begin html ... =end html" you get a Pod​::Block​::Named. That seems ok to me, and maybe we just don't need Pod​::Raw to exist. The only issue is that there needs to be a way to tell the parser that the contents of a block should not be parsed for more Pod, or only selected Pod, like we have for code blocks.

@p6rt
Copy link
Author

p6rt commented Dec 4, 2017

From @softmoth

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​::Block​::Comment. In rakudo/src/Perl6/Pod.nqp the raw_block() routine spits out comments, and is called only for comments from Actions. IMO Pod​::Raw could be removed (and raw_block() renamed comment_block(), I guess).

I note that for something like "=begin html ... =end html" you get a
Pod​::Block​::Named. That seems ok to me, and maybe we just don't need
Pod​::Raw to exist. The only issue is that there needs to be a way to
tell the parser that the contents of a block should not be parsed for
more Pod, or only selected Pod, like we have for code blocks.

In S26, named blocks are introduced by Titlecase identifiers, so

=Html :style-uri('http://example.com/css/pod.css')
<b>This is meant to be unparsed, and used by any processor that wants
to use it</b>

=html
This seems like it should be an error, as I read it​:

S26​:
Note that all block names consisting entirely of lowercase or
entirely of uppercase letters are reserved. See L<#Semantic blocks>.

@p6rt
Copy link
Author

p6rt commented Dec 4, 2017

The RT System itself - Status changed from 'new' to 'open'

@p6rt p6rt added the POD label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant