it was declared that temporaries
are just history.
It is not a big deal any way; can't think of a situation where this
would be useful.
--
David Nicol 816.235.1187
Refuse to take new work - finish existing work - shut down.
nes? Did we consider and reject GCC back end
for reasons beyond "not-devloped-here?"
Inline.pm syntax is fully upgradable to a native back end instead
of invoking external compilers, of course.
--
David Nicol 816.235.1187
.sig file closed by executive order
On Thu, 4 Oct 2001, Michael G Schwern wrote:
> > Backtracking is at the heart of Logic Programming (or Declarative
> > Programming, if you like). This is one of the 3 main programming paradigms
> > (along with procedural and functional). The most popular Declarative
> > language is Prolog. It is
On Thu, 4 Oct 2001, Stephane Payrard wrote:
> Hyper operators with operands of different size are partly covered
> in A3:
>
>
> Hyper operators will also intuit where a dimension is missing from one
> of its arguments, and replicate a scalar value to a list value in that
> dimension. That
On Fri, 5 Oct 2001, Garrett Goebel wrote:
> For those who aren't yet busy reading, you can find it at:
> http://www.perl.com/pub/a/2001/10/03/exegesis3.html
OK, I have a question.
On page 3 you say:
> Because the Perl 6 "diamond" operator can take an arbitrary expression
> as its argument, it'
When you say Unary here:
Binary (low) | Binary (high) |Unary
__|___|_
| |
or | || | |
On Wed, 31 Oct 2001, Damian Conway wrote:
> To me C means: "the *value* stored in the memory
> implementing this variable cannot be changed". Which doesn't preclude
> rebinding the variable to some *other* memory.
>
> But others have a different (and equally reasonable) interpretation of
> C: "th
On Wed, 31 Oct 2001, David Nesting wrote:
> On Tue, Oct 30, 2001 at 09:37:39AM -0500, Aaron Sherman wrote:
> : Yep, but in Perl5, this was never very clean or obvious to the
> : casual programmer. Constants have been coming of age in Perl,
> : and they're kind of scary if the
On Thu, 1 Nov 2001, Garrett Goebel wrote:
> On Wed, 31 Oct 2001, David Nesting wrote:
> > On Tue, Oct 30, 2001 at 09:37:39AM -0500, Aaron Sherman wrote:
> > : Yep, but in Perl5, this was never very clean or obvious to the
> > : casual programmer. Constants have been
On Tue, 16 Oct 2001, David Whipp wrote:
> . I know it uses valuable characters, but adding C to
> identify a query, and C for an operation does not seem
> unreasonable.
What about 'chomp?' for query but 'chomp' (no decoration) for operation?
I think using ? on
On Thu, 21 Feb 2002, Sam Vilain wrote:
> I can't count the number of times I've had to do something like:
>
> if (defined $foo and $foo ne "bar") { }
>
> to avoid my program writing garbage to STDERR.
Of course you will now be able to say:
if ($foo // "" ne "bar") { }
Right?
- D
<[EMAIL PR
On Tue, 4 Jun 2002, Simon Cozens wrote:
> Steve Simmons:
> > We have said that perl5 will be *mostly* mechanically translatable into
> > perl6.
>
> And we shall keep saying this until we believe that it is true?
As a Perl user (the kind of guy who uses Perl at work for everything
humanly possibl
On Mon, 8 Jul 2002, Dan Sugalski wrote:
> Pretty simple. (For illustrative purposes) To do that with
> continuations, it'd look like:
>
> $cont = take_continuation();
> if ($foo) {
> $foo--;
> invoke($cont);
> }
>
> take_continuation() returns a continuation for the curren
How do we intend to manipulate raw binary in Perl6? Perl5's use
bytes; pragma is rather poor (forcing all strings to be raw in its
scope or requiring do {use bytes; ...} type tricks to deal with them)
and now Perl6 has real typing perhaps it would be more usefull to have
a bytestring type (or and
On Sat, 16 Jul 2005 12:14:24 +0800, Autrijus Tang
<[EMAIL PROTECTED]> wrote:
[...]
> On Sat, Jul 16, 2005 at 12:24:21AM +0300, Yuval Kogman wrote:
>> > There is a new generic comparison operator known as ~~.
>>=20
>> ~~ is just Eq, there is also Ord
>
> Hmm, <~ and ~> for generic comparators? ;
On Sat, 23 Jul 2005 23:01:38 +0100, Piers Cawley <[EMAIL PROTECTED]> wrote:
[...]
> It seems to me, that the way to get at all the instances of a class is to ask
> the Garbage Collector to do the heavy lifting for us, and ideally I'd like to
> see this exposed at the Perl level.
I'm going to hij
So the summerizor doesn't get upset with me, I'll restate this in a
seperate thread.
We are should have an API to talk to the GC and give it hints about when it
should run, and tweek the verious paramitors for its running.
For example
use GC trigger => 10`percent;
GC::run(); # Trigger the Gar
Last night I had an idea about a possable pack API. Most likely when
Pugs gets signifigently powerfull I will attempt to implement it.
However I would like everyones input, below is a draft of its POD.
=head1 NAME
Pack - (un)pack structures as defined by a Template
=head1 SYNOPSIS
my Pack $
On Wed, 27 Jul 2005 12:17:52 -0700, Mark A. Biggar <[EMAIL PROTECTED]> wrote:
> Larry Wall wrote:
[...]
>> Whatever we call
>> it, this type/class/role/subtype has to admit Item and Pair objects
>> but not Junctions. (And if that's the wrong way to think about it,
>> please tell us why.)
>
> S
On 26 Jul 2005 05:18:05 -, David Formosa )
<[EMAIL PROTECTED]> wrote:
> We are should have an API to talk to the GC and give it hints about when it
> should run, and tweek the verious paramitors for its running.
>
> For example
[...]
Also
my Bigobjet $big is GC:
On Thu, 28 Jul 2005 16:22:19 +0300, Yuval Kogman <[EMAIL PROTECTED]> wrote:
[...]
> On Thu, Jul 28, 2005 at 01:08:13 -0000, David Formosa (aka ? the Platypus) =
> wrote:
[...]
>> my Bigobjet $big is GC::timely =3D Bigobect; # Request timely
>> # destruction of $big.
On Thu, 28 Jul 2005 15:46:14 +0300, Yuval Kogman
<[EMAIL PROTECTED]> wrote:
[...]
> I like your Pack object - that is the parsed template, but I'd also
> like to be able to generate these templates with a programmatic
> interface that isn't string concatenation...
>
> Is it just a simple data st
I was thinking about lazyness and IO and worked out this potenial
gotcha. In essence its quite simmler to the pipe buffering problems
you sometimes can get in perl5.
my IO $news = io("nntp://nntp.perl.org",:rw); # Open a nntp connection
my $banner = =$news # Throw away the banner. So far so goo
On Mon, 01 Aug 2005 22:08:52 +0300, Yuval Kogman
<[EMAIL PROTECTED]> wrote:
[...]
> On Mon, Aug 01, 2005 at 08:46:07 -0700, Greg Buchholz wrote:
>
>> Has any thought been given to using a concurrent garbage collector
>> for Perl6? Besides eliminating GC pauses (which in turn means less of a
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 Mon, 15 Aug 2005 12:40:05 +0100, Adrian Howard <[EMAIL PROTECTED]> 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]
>
>
On Mon, 15 Aug 2005 15:17:18 +0300, Yuval Kogman <[EMAIL PROTECTED]> wrote:
[...]
>> 2) Some way of being able to tell the garbage collector to ignore
>> the current contents of the heap for the purposes of GC. One
>> Pop-11 idiom was to do something like:
[...]
> We are trying to design a re
On Tue, 16 Aug 2005 20:14:43 +0300, Yuval Kogman <[EMAIL PROTECTED]> wrote:
[...]
> Let's define some terms:
These are all very good and I'm going to incorprate them in the API docs.
> scope/origin - where objects are created
I would refine this one.
origin scope - The lexical scope
On Tue, 16 Aug 2005 19:46:29 +0300, Yuval Kogman <[EMAIL PROTECTED]> wrote:
[...]
> On Tue, Aug 16, 2005 at 05:32:50 -0000, David Formosa (aka ? the Platypus) =
> wrote:
>> > This is getting me thinking though:
>> >=20
>> >$*RUNTIME.Memory.Garbag
On Thu, 09 Jan 2003 21:12:07 -0500, John Siracusa
<[EMAIL PROTECTED]> wrote:
[...]
> Hey, it adds up! Okay, maybe it doesn't...but still, Perl 6 Should Be Able
> To Do This! :) And I'd also like inline constructs like:
>
> ASSERT $foo > 5 && is_happy(blah);
macro debug ($code) is parsed
On Wed, 24 Aug 2005 16:13:03 +0300, Yuval Kogman <[EMAIL PROTECTED]> wrote:
[...]
> perl6 creates a new instance of the perl compiler (presumably an
> object). The compiler will only compile the actual file 'foo.pl',
> and disregard any 'require', 'use', or 'eval' statements.
use has the potenti
On Thu, 25 Aug 2005 16:25:51 +0300, Yuval Kogman <[EMAIL PROTECTED]> wrote:
[...]
> On Thu, Aug 25, 2005 at 11:16:56 -0000, David Formosa (aka ? the Platypus) =
> wrote:
[...]
>> use has the potentional to change the way the compiler
>> parses the code. So use needs
On Fri, 14 Oct 2005 08:38:55 +0200, Peter Makholm <[EMAIL PROTECTED]> wrote:
> Yesterday I spend some hours getting pugs to understand
> translitterations with multiple ranges in each pair. E.g.
>
> "foobar".trans( "a-z" => "n-za-n" );
>
> By accident I tested something like:
>
> "foobar".t
--
Please excuse my spelling as I suffer from agraphia. See
http://dformosa.zeta.org.au/~dformosa/Spelling.html to find out more.
Free the Memes.
On Fri, 10 Jun 2005 11:58:31 +0200, Juerd <[EMAIL PROTECTED]> wrote:
> David Formosa (aka ? the Platypus) skribis 2005-06-10 9:32 (-):
>>
>
> Interesting. Could you provide some more information, like perhaps a
> message body?
My appologies, my news client cra
This is inspired inpart by discussions I had on #perl6.
Basically what is the behavour of the hyperop when applied to two
hashes. The concensus was that the hashes would get unrolled into
lists, and the pairs would get matched up more or less randomly.
I don't feel that this is a
On Tue, 14 Jun 2005 07:19:09 -0700, Mark A. Biggar <[EMAIL PROTECTED]> wrote:
> Luke Palmer wrote:
>> On 14 Jun 2005 06:07:10 -, David Formosa (aka ? the Platypus)
>> <[EMAIL PROTECTED]> wrote:
>>>multi sub infix_circumfix_meta_operator:{
On Thu, 30 Jun 2005 05:17:56 +0300, Yuval Kogman
<[EMAIL PROTECTED]> wrote:
[...]
> I gave Perl 6 to Mr. Clean, and he said that if type inferrence was
> formalized, and used always, except that it's usually used for
> performance, and with a lexical pragma can be used to enforce types.
> I like
I'm just wondering if a documentation trait on subs would be usefull.
If we are going to have something like p6explain the doc trait could
be used as the source for the infomation for it. p6explain would
simply have to walk the AST reading the doc traits and pasting the
text together.
--
Please
On Thu, 30 Jun 2005 18:53:44 +0200, Stéphane Payrard
<[EMAIL PROTECTED]> wrote:
> On Thu, Jun 30, 2005 at 06:17:14AM -0000, David Formosa (aka ? the
Platypus) wrote:
[...]
>> I would prefur this to be written.
>>
>> use strict "types";
>>
>
&
leness standard which has appeared in
the ensuing years)
david nicol
1001 - 1041 of 1041 matches
Mail list logo
