> # Pugs - Lambda Camels
> http://pugscode.org/images/lambdacamels.png
I wonder do greek symbols have any meaning?
I was expecting to see greek letters in a sequence of: pi, epsilon, rho,
lambda, so it could likely to be spelled as "perl"
In other words, "\x{03c0}\x{03b5}\x{03c1}\x{03bb}"
On Mon, Aug 15, 2005 at 02:03:22PM +0400, Konovalov, Vadim wrote:
> > # Pugs - Lambda Camels
> > http://pugscode.org/images/lambdacamels.png
>
> I wonder do greek symbols have any meaning?
Yes, "omega" stands for higher-order polymorphism, as in
"System F-omega".
The reversed "E" is the
Applied (8965).
After a very fruitful discussion I've rewritten my suggested GC API.
Comments please. Is this the path we should be going down? What
needs more work? What needs clarification? Have I totally lost the
plot?
=pod
=head1 NAME
GC - The interface to the runtime Garbage collector.
=head1 SYNOPSI
On 15 Aug 2005, at 02:13, David Formosa ((aka ? the Platypus)) wrote:
After a very fruitful discussion I've rewritten my suggested GC API.
Comments please.
[snip]
I'm speaking from complete ignorance since I've only been vaguely
following the subject... but four additional things that strike
On Mon, Aug 15, 2005 at 12:40:05 +0100, Adrian Howard wrote:
> On 15 Aug 2005, at 02:13, David Formosa ((aka ? the Platypus)) wrote:
>
> >After a very fruitful discussion I've rewritten my suggested GC API.
> >Comments please.
> [snip]
>
> I'm speaking from complete ignorance since I've only been
On Tue, Jul 05, 2005 at 06:47:41PM -0600, zowie wrote:
> There is also a certain joy that comes from noticing that a tool was
> designed by pedants:
> it's great that cal(1) handles the Gregorian reformation correctly
> (or at least, in one
> of several arguably correct ways) even though most
On 2005-08-15 10:07, "Nicholas Clark" <[EMAIL PROTECTED]> wrote:
> Spain adopted the Gregorian Calendar in 1582. Surely setting my locale to
> Spain should make the Julian/Gregorian jump show up in 1582, not 1752?
Arguably so, but I don't think there's anywhere in the POSIX localization
data struc
On 15 Aug 2005, at 13:17, Yuval Kogman wrote:
On Mon, Aug 15, 2005 at 12:40:05 +0100, Adrian Howard wrote:
[snip]
1) Some way of declaring objects as being "fixed" so we can pass
them to external code without having to worry about the GC moving
them around.
A handle to an object should a
On Sun, Aug 14, 2005 at 08:28:33PM +0800, Autrijus Tang wrote:
: S06 made many explicit uses of generics as classes, which I find
: difficult to reconcile with the "only roles takes type parameter"
: ruling. For example:
:
: my Hash of Array of Recipe %book;
: my Hash[returns=>Array[retur
Hello all,
I have posted this question on CPAN Forum but nobody answered, so I
also post it here in case someone has an idea.
While rewriting Net::Pcap test suite, I quickly stumbled upon this
problem: it looks like Test::Exception can't catch croak() or die()
thrown from XS code. Here is an
* Sébastien Aperghis-Tramoni wrote:
>While rewriting Net::Pcap test suite, I quickly stumbled upon this
>problem: it looks like Test::Exception can't catch croak() or die()
>thrown from XS code. Here is an example:
http://spo.sf.net uses Test::Exception and croak() and things seem to
work for me
Sébastien Aperghis-Tramoni wrote:
While rewriting Net::Pcap test suite, I quickly stumbled upon this
problem: it looks like Test::Exception can't catch croak() or die()
thrown from XS code.
[...]
Ok, I corrected a mistake (I was using dies_ok() instead of
throws_ok()), and reduced the probl
On Mon, Aug 15, 2005 at 05:58:23PM +0200, S?bastien Aperghis-Tramoni wrote:
> use strict;
> use Test::More tests => 2;
> use Test::Exception;
> use Net::Pcap;
>
> throws_ok(
> sub { Net::Pcap::lookupdev() },
> '/^Usage: Net::Pcap::lookupdev\(err\)/',
> "
Yitzchak Scott-Thoennes wrote:
The throw_ok { ... } syntax only works because the throw_ok sub exists
and has a prototype that specifies a subref is expected; if you don't
load Test::Exception by the time the throw_ok call is compiled, it
is parsed as an indirect object call of the "throw_ok" me
Nicholas Clark wrote:
On Tue, Jul 05, 2005 at 06:47:41PM -0600, zowie wrote:
There is also a certain joy that comes from noticing that a tool was
designed by pedants:
it's great that cal(1) handles the Gregorian reformation correctly
(or at least, in one
of several arguably correct ways) ev
On 2005-08-15 13:07, "Mark A. Biggar" <[EMAIL PROTECTED]> wrote:
> 3) use Astronomical Dates which are kept as the number of days sense
> noon Jan-1-4713 BC.
More specifically, that's the astronomical Julian Day, or JD, and JD 0 began
at noon Universal Time (a.k.a. GMT) on January 1, 4713 BC in th
On Mon, Aug 15, 2005 at 08:19:38AM -0700, Larry Wall wrote:
> I think the distinction is still useful to document that there are
> still unbound types. What we need to emphasize is that a role can be
> used as a class, at which point any unbound types are bound to Any,
> or whatever we're calling
On Tue, Aug 16, 2005 at 01:33:56AM +0800, Autrijus Tang wrote:
: On Mon, Aug 15, 2005 at 08:19:38AM -0700, Larry Wall wrote:
: > I think the distinction is still useful to document that there are
: > still unbound types. What we need to emphasize is that a role can be
: > used as a class, at which
On Mon, Aug 15, 2005 at 10:43:45AM -0700, Larry Wall wrote:
> : So the last line means a role can be used just like a class, and
> : _inherit_ its behaviour as well?
> :
> : role Point { has $.x; has $.y; method move_right { $.x++ } };
> : role MyPoint is Point {
> : method move_right
At 13:31 -0400 8/15/05, Mark Reed wrote:
>More specifically, that's the astronomical Julian Day, or JD, and JD 0 began
>at noon Universal Time (a.k.a. GMT) on January 1, 4713 BC in the Julian
>calendar. Sometimes this is called the Julian Astronomical Day, or JAD, to
>distinguish it from various o
On Wed, Jul 13, 2005 at 06:07:55PM +1000, Damian Conway wrote:
> The use of summed lineal distance (L[1]) rather than RMS distance (L[2])
> probably *isn't* superior as a closeness measure. But it's computationally
> much simpler (and hence likely to be more efficient), it doesn't suffer
> from
Perl 6 will natively think of dates as number of floating point TAI
seconds from the year 2000. You can build any kind of date interface
on top of that, but we're going for simplicity and predictability.
If UTC goes ahead with with additional leap seconds, we will NOT use
Posix stretchy seconds t
On 15 Aug 2005, at 17:12, Yitzchak Scott-Thoennes wrote:
[snip]
The throw_ok { ... } syntax only works because the throw_ok sub exists
and has a prototype that specifies a subref is expected; if you don't
load Test::Exception by the time the throw_ok call is compiled, it
is parsed as an indirect
On Tue, Aug 16, 2005 at 01:49:02AM +0800, Autrijus Tang wrote:
: Aye. But if a Role can be inherited _from_, then this should
: work too, right?
:
: role Point {
: has $.x; has $.y;
: method move_right { $.x++ }
: };
: role OurPoint is Point {
: method move_right { .
On 2005-08-15 15:04, "Doug McNutt" <[EMAIL PROTECTED]> wrote:
> At 13:31 -0400 8/15/05, Mark Reed wrote:
> If anyone gets serious about Julian dates there is also the Modified Julian
> Date, MJD, used by the US military and others. It differs from the JAD above
> by a large well-defined integer p
On 2005-08-15 13:56, "Larry Wall" <[EMAIL PROTECTED]> wrote:
> I'm personally rooting for everyone to abandon leap seconds for civil time.
While you're at it, why not wish for DST to go away (or to become permanent
year-round, whichever)? Heck, toss in world peace, too. :)
> But POSIX stretchy s
On 2005-08-15 13:56, "Larry Wall" <[EMAIL PROTECTED]> wrote:
> Perl 6 will natively think of dates as number of floating point TAI
> seconds from the year 2000. You can build any kind of date interface
> on top of that, but we're going for simplicity and predictability.
I applaud that decision.
The Perl 6 Summary for the week ending 20050814
As you will note from the date in the title, it's been a short week.
We're switching back to a midnight Sunday/Monday rollover in order to
make life easier for the perl.com types. So, if I can avoid being
distracted too much by the sec
On Mon, Aug 15, 2005 at 04:41:03PM -0400, Mark Reed wrote:
: On 2005-08-15 13:56, "Larry Wall" <[EMAIL PROTECTED]> wrote:
: > Perl 6 will natively think of dates as number of floating point TAI
: > seconds from the year 2000. You can build any kind of date interface
: > on top of that, but we're g
On Mon, 2005-08-15 at 16:33 -0700, Larry Wall wrote:
> : I would assume that you would choose time 0.0 = Jan 1, 2000 at 00:00:00.0
> : TAI (December 31, 1999 at 23:59:29.0 UTC), making the whole thing free of
> : any UTC interferences. But there is an argument for making the zero point a
> : reco
On Tue, Aug 16, 2005 at 01:18:58PM +1200, Sam Vilain wrote:
: On Mon, 2005-08-15 at 16:33 -0700, Larry Wall wrote:
: > : I would assume that you would choose time 0.0 = Jan 1, 2000 at 00:00:00.0
: > : TAI (December 31, 1999 at 23:59:29.0 UTC), making the whole thing free of
: > : any UTC interfere
32 matches
Mail list logo
