Issues encountered:
Documentation
Execution
Issues encountered:
Documentation
Execution
#!/bin/env raku | |
use PDF::Lite; | |
use PDF::Font::Loader; | |
use lib "./lib"; | |
use Subs; | |
my enum Paper <Letter A4>; | |
my $debug = 0; |
#!/usr/bin/env raku | |
my $ucd-ver = '10.0'; # use same as rakudo | |
my $ucd-dir = "./UCD.v{$ucd-ver}"; | |
my $ucd = 'UnicodeData.txt'; | |
my $fi = "$ucd-dir/$ucd"; | |
my $fo = 'space-chars.list'; | |
my $fh = open $fo, :w; | |
my @v; |
Pseudo code for setting a domain's host records via its registrar's API: | |
----------------------------------------------------------------------- | |
=== Given three physical servers: | |
host servers' FQDN, IPv4, and role: | |
---------------------------------- | |
host2.mydom.net - 2.2.2.1 - web server | |
host4.mydom.net - 4.4.4.1 - backup mail server | |
host6.mydom.net - 6.6.6.1 - primary mail server and |
The following text is a verbatime quote from an e-mail received from Damian Conway in response to my asking him for his view on legitimate values for pod configuration keys:
My intention was always that the meaning of adverbials in Perl 6 Pod
should be exactly the same as everywhere else in Perl 6. Hence:
:a{} ---> 'a' => %empty-hash
:b() ---> 'b' => ()
:c('') ---> 'c' => ''
This is a proposal for reorganizing some of the current Rakudo NQP code in order to ease maintenance by separating, to the extent possible, grammar and actions pod-only code handling from the rest of the code. The proposal is an interim step toward a future step of a separate slang (sublang) for pod.
The current organization of pertinent parts of the code in the Rakudo repo directory src/Perl6/ looks like this
$ ls -1
Actions.nqp
Grammar.nqp
# code fragment in rakudo's src/Perl6/Grammar.nqp | |
token numbered-alias { '#' } | |
my $*USE-HASH-MARK := 1; # default, means we're free to extract the first '#' in a pod block's data | |
# inside a pod block, e.g., abbreviated, paragraph, or delimited | |
# following the configuration, if any | |
{ |
/usr/bin/perl tools/build/check-nqp-version.pl /usr/local/people/tbrowde/mydata/tbrowde-home-bzr/perl6/perl6-repo-forks/rakudo/install/bin/nqp-m | |
rm -f -- perl6 | |
cp -- perl6-m perl6 | |
chmod -- 755 perl6 | |
/usr/bin/perl t/harness5 --fudge --moar --keep-exit-code --verbosity=1 t/spec/S32-list/seq.t | |
t/spec/S32-list/seq.rakudo.moar .. | |
1..41 | |
ok 1 - seq => array works 1 | |
ok 2 - We didn't flatten the RHS because it's no single argument | |
ok 3 - Seq stayed intact |
There are several instances of some old regex syntax in the current rakudo grammar. | |
From a brief answer by @timotimo, I'm assuming those instances can be changed to: | |
<tok>**1 [1 use; require one instance of the token?; change to =>] <tok> | |
<tok>**0..1 [17 uses; require none or one?; change to =>] <tok>? |