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
Formatting codes does not work inside declarator blocks #4754
Comments
From @teodozjanExamples in spec http://design.perl6.org/S26.html#Declarator_blocks use v6; output: This is perl6 version 2015.10-323-gb18ada0 built on MoarVM version 2015.10-92-g0181385 |
From @LLFourn#| look it's a C<thing>! say &thing.WHY.contents.perl; #-> ["look its a C<thing>"] |
From @lizmat
Feels like ENOTABUG to me. What does �parse as POD� even mean in this context? It�s a string that *could* be interpreted as pod. But it�s still just a Str. It�s entirely up to you what you do with it. Standard tools will use it *as* pod, yes. But at the .WHY level, it�s just a Str. Well, anyway, that�s my interpretation of it :-) Liz |
The RT System itself - Status changed from 'new' to 'open' |
From @LLFournHey Liz, The thing is that it seems that it isn't pod at any level. It simply isn't I would love to be wrong :) LL On Fri, 18 Dec 2015 at 9:49 PM, Elizabeth Mattijsen via RT <
|
From @lizmatI was completely wrong in assuming that .WHY returned a Str. So this probably is a bug, but for someone else to fix, as I�m a complete pod 6 noob. Liz
|
From @teodozjanNot the same but similar |
From @LLFournThat is caused by the same thing. Thanks! On Sun, 20 Dec 2015 at 4:20 AM, Kamil Ku�aga via RT <
|
From @hoelzroFor example: #| Here I<I> am say(&foo.WHY.Str); # Here I<I> am |
From @LLFournThere are now three of these XD. https://rt.perl.org/Public/Bug/Display.html?id=126954 FYI this is really difficult to implement with pod in its present state. On Sun, Jan 17, 2016 at 2:25 PM Rob Hoelz <perl6-bugs-followup@perl.org>
|
The RT System itself - Status changed from 'new' to 'open' |
From @hoelzroI haven't looked at SUPERNOVA much, but I think this should actually be pretty simple to fix. The comment:sym<#|> token and friends need to be updated to use the pod_content rule. If I have enough time this week, I may end up doing this. On 2016-01-16 20:36:48, lloyd.fourn@gmail.com wrote:
|
From @LLFournI have also been down this path. The one line version is doable as you The trick is getting: On Sun, Jan 17, 2016 at 4:52 PM Rob Hoelz via RT <
|
From @LLFournForgot, the tricky one is really: #|{ docs for sub { } are in here } sub foo { } ^^ That should be fine and parses properly now. IMO just making the one On Sun, Jan 17, 2016 at 4:58 PM Lloyd Fournier <lloyd.fourn@gmail.com>
|
I would say that this is similar to #2863 (maybe it's mentioned somewhere, since links don't work now...). |
Migrated from rt.perl.org#126654 (status was 'new')
Searchable as RT126654$
The text was updated successfully, but these errors were encountered: