Re: Perl6 Operator List, Take 3
On Mon, 28 Oct 2002 13:09:37 -0800 (PST), Larry Wall [EMAIL PROTECTED] wrote: How do your read $a ! $b ! $c? Neither $a nor $b nor $c. What? Aren't you able to see this invisible neither operator just at the front? ;-) /L/e/k/t/u
Re: Tagmem* (was Unary dot)
On Tue, 16 Apr 2002 09:34:36 -0700 (PDT), Larry Wall [EMAIL PROTECTED] wrote: Pike predates Dawkins, who I believe made up the term. (Could be wrong about that.) They are similar concepts, however, in that a tagmeme is a psychological linguistic construct that propagates culturally. It's certainly possible that Dawkins read Pike. But it's also quite likely that he didn't, and made up meme as a portmanteau on gene and memory. On _THE SELFISH GENE_ Dawkins says he coined the term, which was a more euphonic version of mimeme: http://www.santafe.edu/~shalizi/formerly-hyper-weird/memetics.html /L/e/k/t/u
Re: What can we optimize (was Re: Schwartzian transforms)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 29 Mar 2001 10:36:48 -0800, "Hong Zhang" [EMAIL PROTECTED] wrote: The function in Ada can not have any side effect, i.e. no change to globals. Unless my reading of the Ada 95 standard is wrong, there's nothing that precludes functions having side effects. The only thing an Ada function cannot do is having "out" or "in out" parameters, so it cannot modify its arguments, and even that can be circumvented (as you can pass "in" access parameters). /L/e/k/t/u -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.8 for non-commercial use http://www.pgp.com iQA/AwUBOsOiu/4C0a0jUw5YEQKjQwCeP2Aeu6aJsdpP3asvcQDS+dyk2aoAoKS5 2gJ1o0xX1lfa0hXrVff1tPvx =t4je -END PGP SIGNATURE-
The Unlambda Programming Language
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 19 Feb 2001 13:17:56 -0600, "David L. Nicol" [EMAIL PROTECTED] wrote: "currying" used in a fascinating context: an experimental language in which http://www.eleves.ens.fr:8080/home/madore/programs/unlambda/#tut In that vein, perhaps (the collective) you wants to visit the Esoteric Languages' page of Cat's Eye Technologies: http://www.catseye.mb.ca/ /L/e/k/t/u -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.8 for non-commercial use http://www.pgp.com iQA/AwUBOpJ9Cv4C0a0jUw5YEQJFwgCfXc6USTxBcJHbf0vSagVu9ofNVL0AnjN/ TwaFtv8MxYM+mCFp87PlKChe =0iQ+ -END PGP SIGNATURE-
Re: RFC 85 (v1) All perl generated errors should have a
On 10 Aug 2000 22:26:47 -, Chaim Frenkel [EMAIL PROTECTED] wrote:
=head2 Encodings
I have listed some possiblities. But none of these are ideal.
=head3 A unique number
=item As an integer
=item As a floating point number
=head3 Unique String
=head3 Prefixes for all error strings (Shades of Big Blue)
Well, $@ could also contain a structured 'error object' allowing
not only stringification, for
if( $@ =~ /such-and-such-error/ ) {}
situations, but also (somewhat à la VMS):
$@-facility # CORE, module name, whatever
$@-severity # fatal, informational, error, debug...
$@-message# 'file %s not found' (== stringify)
$@-data # an optional hash for additional data
Obviously, to be useful a standard classification of severity levels
(akin to the one in diagnostics) should be used, and it'd be better
if there were some hooks for modules to register unique facility
names; OTOH, perhaps not: the module name *is* it's own unique
identifier :)
/L/e/k/t/u
