On Mon, Mar 13, 2006 at 09:37:47AM -0800, Larry Wall wrote:
: On Mon, Mar 13, 2006 at 08:28:46AM -0800, Larry Wall wrote:
: : The default answer should probably be yes,
:
: Or maybe not... After all, the main point of taking a reference is
: to nail down particulars so you can bypass the identifi
On Mon, Mar 13, 2006 at 08:28:46AM -0800, Larry Wall wrote:
: The default answer should probably be yes,
Or maybe not... After all, the main point of taking a reference is
to nail down particulars so you can bypass the identification phase
next time and deal directly with your object (or proxy ob
Hmm, if almost everything desugars to function/method calls, and we
have a generic .wrap mechanism in addition to the MMD mechanism, then
the only remaining technical question is whether you can actually
name the function or method (or set of multimethods) to which the
surface code is being desugar
I have two stories related to files. I'll start with the failure:
I wanted to write a Test::Harness wrapper that would monitor all the
files/directories that the .t files of my test suite opened, and
when they change to rerun only the affected tests.
I am still planning on hacking this unportably
Hi,
In light of the Perl 6 community's increasing interest in API level
design, I'd like people to share old war stories about things they
had to do once, but had to jump through hoops to pull off.
The point of this excercise is the edge cases of the existing perl
builtin functions and core modul
