A. Pagaltzis (paga...@gmx.de)

* Yuval Kogman <nothingmuch@woobling.org> [2008-09-04 16:20]:
> C<git help> lists common commnads
                              ^^^^
Typo.

> =head3 delete
>
> C<git rm>

Note: this is not mandatory. You can actually delete the file in
any way you like, like plain old `rm`, as long as you update the
index to denote this, eg. with `git add -u`. Using `git rm` just
integrates both parts of the process into a single step.

> C<git pull> fetches changes and merges them using C<git rebase>.

*cough* *sputter* Whuh…? No, it uses `git merge`. Of course you
can tell `git pull` to rebase using the `--rebase` switch, but
this is explicit, as it should be, because rebasing rewrites
history, whereas merging does not.

Regards,

* Nicholas Clark <nick@ccl4.org> [2008-09-02 20:30]:
> But I've tried touting this task before, and everyone seems
> instantly busy.

I can see why.

I can tell you some trivial things that have *not* changed, which
is all of `~~`’s spec outside of that section, such as
precedence, interaction with `when`, exception matching, etc. pp.
This is so easy to figure out that I assume everyone else before
me who may have attempted this task has also figured out this
much, and that my work so far has therefore produced no value.

That leaves the Smart Matching sections themselves. In Feb 2006,
the section was 80 lines long. It has quadrupled since. This’ll
take a rather long chunk of quality time to figure out.

> So it would be useful for someone to compare the Perl 6
> smartmatch table as of February 2006
> L<http://svn.perl.org/viewvc/perl6/doc/trunk/design/syn/S03.pod?view=markup&pathrev=7615>
> and the current table
> L<http://svn.perl.org/viewvc/perl6/doc/trunk/design/syn/S03.pod?revision=14556&view=markup>
> and tabulate the differences in Perl 6.

Actually, the old table was in S04 @7615, with a note saying it
should be in S03.

> The annotated view of changes is
> L<http://svn.perl.org/viewvc/perl6/doc/trunk/design/syn/S03.pod?view=annotate>
> and the diff is
> C<svn diff -r7615:14556 http://svn.perl.org/perl6/doc/trunk/design/syn/S03.pod>
> -- search for C<=head1 Smart matching>. (In theory F<viewvc>
> can generate that, but in practice when I tried it hung
> forever, I assume "thinking")

Even the annotate link hangs until it times out, for me. Not that
in either case it matters, because the table moved from S04 to
S03 in the meantime, so both the diff and annotate views are
actually completely useless. Since the section has grown several
times I’ll assume here that shaving yaks with git-svn to get a)
acceptable performance with b) a local repo browser, will only
lead me to discover that following diffs over time is no more
helpful than reading the two revisions in isolation and entirety.
Therefore I am reading them thusly.

I’ll report back with my findings.

Regards,

But then ~~ against a string in list context would be different
from ~~ against a regex in list context. Is it more important
for ~~ to be consistent with =~ or more important for it to be
consistent with itself? (This is not a rhetorical question. I
suppose the answer is “itself,” but I have not thought of any
solid argument other than that self-consistency for the sake
of self-consistency is an obvious-seeming right choice.)

Regards,

Hi Nicholas,

* Nicholas Clark <nick@ccl4.org> [2008-03-25 23:00]:
> Someone else correct me if I'm wrong, but as I understand it,
> if you start your script ./rakkk
>
> #!/usr/bin/perl -w
>
> then often perl is invoked by the shell as
>
> /usr/bin/perl -w ./rakkk

no, it’s the kernel that does that, automatically. The shell has
nothing to do with it.

The reason perl parses the switches again is that it might be
invoked in some other fashion than implicitly via the shebang
under a Unixoid kernel; eg. the user types `perl ./rakk` into
the shell. In such a case, the shebang line options would fail
to have an effect if perl didn’t parse them.

> and that -w is set and processed before the script is opened.
> But then perl reads in the first line of the script, and
> processes the -w again (using Perl_moreswitches()). But for all
> the command line options that can be used on the #! line, it
> doesn't matter if they are processed multiple times)

Yeah, that’s why you can’t use -M on the shebang line. It’s also
obvious why you can’t use -T, even though that’s for a different
reason. It’s not so obvious why 5.10 has promoted -C to this
club, though.

Regards,

    use open OUT => ':utf8', ':std';

Regards,