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
Implement $=data for Pod data blocks #3029
Comments
From kevin@dawson10.plus.comHi All, ticket as requested by FROGGS the info in -> http://perl6.org/compilers/features relating to Lexing and Parsing - Pod implies all works, But This is not the case Data Blocks from - http://perlcabal.org/syn/S26.htm Data blocks <http://perlcabal.org/syn/S26.html#___top> Named Pod blocks whose typename is |data| are the Perl 6 equivalent of There is a corresponding variable, |$=data|, from which each |=data| Each |=data| block can be given a |:key| option, to name it. The =begin data :key<Virtues> say 'The three virtues are:'; The contents of any |=data| block that does not have a |:key| are say 'The second anti_Virtue is: ', $=data[1]; =data Industry Note that, as the preceding example illustrates, because Pod is a When |$=data| itself is stringified, it returns the concatenation of all |=data| blocks are never rendered by the standard Pod renderers. We Now Generate the following Output: $ perl6 data_blocks.p6 regards |
From kevin@dawson10.plus.comuse v6; =begin data :key<Virtues> say 'The three virtues are:'; say 'The second anti_Virtue is: ', $=data[1]; =data Industry |
From bowtie@cpan.orghttps://github.com/perl6/features/blob/master/features.json#L908 "status" : "r+ n+- (parsing only, no $=pod)", could be changed to "status" : "r+- n+- (parsing only, no $=pod)", regards I don't know |
@usev6 - Status changed from 'new' to 'open' |
From @usev6I'll modify the feature matrix at http://perl6.org/compilers/features to reflect the missing implementation of $=data for Pod data blocks. |
Message now is:
|
Migrated from rt.perl.org#116419 (status was 'open')
Searchable as RT116419$
The text was updated successfully, but these errors were encountered: