Hi Mark,
What does the fix to 't/codingstd/c_indent.t' do? Does it ignore anything
inside #ifdef __cplusplus blocks?
Regards,
Senaka
On Sat, Apr 19, 2008 at 6:38 AM, Mark Glines via RT <
[EMAIL PROTECTED]> wrote:
> On Thu Apr 17 09:03:57 2008, infinoid wrote:
> > On Tue Apr 15 02:58:18 2008, [E
On Mon Apr 14 21:50:00 2008, infinoid wrote:
> At first glance, the only difference I can see is that your cast removes
> the "const" attribute. But instead of doing that, I'm wondering if
> maybe the second argument of VTABLE_isa(interp, pmc, name) should be
> made const, instead. Would that hel
Dave Whipp dave-at-whipp.name |Perl 6| wrote:
>
> Since the method name (but nothing else) is known at class
> construction time, the following .wag method is autogenerated for you:
>
>method wag (|$args) { $!tail.wag(|$args) }
...
Another thing that might be nice (maybe not a perl 6.0.0 f
Great. So the flip side is, what do I return from a function so that it
gives a single value if called simply, but provides optional named
returns that are there if you catch them? As a capture with one
positional and one named argument?
And how do you declare =that= return type ("of" type)
If a function returns different things if called in list context or
item context, how do you define the "of" type (outer return type) to
make the function strongly typed?
How about sub foo (--> Seq^Item) {...}?
Interesting idea, but that doesn't tell the compiler that the return is
keyed t
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
sub foo ($x) {...}
$x = &foo.new(3);
I don't understand your point. Are you thinking of .callwith or
postcircumfix<( )> methods on the Code object?
No, I think of foo not as a Code object but as a class that
does Code. Invoking foo mea
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
Sorry, I see no contradiction. Method doit *is* a parametric type.
That is you need a type argument to make a code type. And then
you need args to make an invocation. Now the question is who provides
the type argument and when. An explicit instanc
On Friday 18 April 2008 13:42:01 [EMAIL PROTECTED] wrote:
> Added: trunk/languages/lua/src/lib/bc.pir
> ===
> --- (empty file)
> +++ trunk/languages/lua/src/lib/bc.pir Fri Apr 18 13:42:00 2008
> +.sub 'get' :anon
> + .par
I noted Jonathan Worthington's work implementing the "handles" trait for
delegation through attributes, and was a bit surprised to see that it is
defined (S12/delegation) to use strings instead of method signatures --
I had thought that perl6 was attempting to be symbolic in places where
perl5
On Fri, Apr 18, 2008 at 12:47 PM, chromatic <[EMAIL PROTECTED]> wrote:
>
> On Friday 18 April 2008 07:45:43 Patrick R. Michaud wrote:
>
> > On Fri, Apr 18, 2008 at 06:30:24AM -0700, Stephane Payrard wrote:
> > > The error message is "No such caller depth"
>
> > > Having it working would be a add
On Wed, Apr 16, 2008 at 05:53:45PM -0500, Miller, Hugh wrote:
: Is there something for perl analogous to the sort of formal presentation
: seen in e.g., Robin Milner's "Definition of Standard ML" ?
The closest we've gotten to anything "formal" is what John is working
on right now. We've historica
On Fri, Apr 18, 2008 at 07:22:35PM +0200, TSa wrote:
> HaloO,
>
> I just wonder what has become of the coroutine feature.
> Was that dropped from the spec? And when yes, why?
Coroutines have never been in the official spec, except in the
form of gather/take. Pugs implements coro, and the draft I/
HaloO,
I wrote:
sub foo () { my $x = 0; yield $x++; }
I meant:
sub foo () { my $x = 0; yield $x++ while 1;
--
"The unavoidable price of reliability is simplicity"
-- C.A.R. Hoare
HaloO,
I just wonder what has become of the coroutine feature.
Was that dropped from the spec? And when yes, why?
The trick is to design the yield statement nicely.
And also to define a syntax that allows to get a fresh
instance from a coro quasi-class.
sub foo () { my $x = 0; yield $x++; }
On Wed, Apr 16, 2008 at 07:51:03PM -0500, John M. Dlugosz wrote:
> No, *@ is the slurpy array parameter. I was thinking of
>
> (*,*,$x) = @array; # skips first two elements
>
> to suppose that @* might mean "no name" if the syntax would not allow for
> bare @ there without an identifier.
On Fri, Apr 18, 2008 at 05:34:25AM -0500, John M. Dlugosz wrote:
> If a function returns different things if called in list context or item
> context, how do you define the "of" type (outer return type) to make the
> function strongly typed?
You can't. An "of" type forces the function into a si
On Friday 18 April 2008 07:45:43 Patrick R. Michaud wrote:
> On Fri, Apr 18, 2008 at 06:30:24AM -0700, Stephane Payrard wrote:
> > The error message is "No such caller depth"
> > Having it working would be a additional tool.
> > Indeed, I wanted to tweak the code manually to see the code I needed
On Fri, 2008-04-18 at 05:10 -0700, James Keenan via RT wrote:
> I'll consider this patch, but, as all the other code in this module has
> corresponding unit tests, we'll have to write a test for it. It should
> go in whatever t/configure/*.t file holds other tests for
> Parrot::Configure::Options:
On Fri, 2008-04-18 at 06:26 -0700, Andy Dougherty via RT wrote:
> > +my $these_tests = $steps_tests{$temp[0]}{$temp[1]}
> > +or croak "No tests exist for configure step $step";
>
> Thank you. That's definitely an improvement. I know I wasted a lot
> of time trying to figure out what
On Fri, Apr 18, 2008 at 06:30:24AM -0700, Stephane Payrard wrote:
> The error message is "No such caller depth"
>
> Having it working would be a additional tool.
> Indeed, I wanted to tweak the code manually to see the code I needed
> the rakudo compiler to generated.
>
> I have not investigated
# New Ticket Created by Stephane Payrard
# Please include the string: [perl #53040]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53040 >
The error message is "No such caller depth"
Having it working would be a additional
On Thu, 17 Apr 2008, Geoffrey Broadwell wrote:
> # New Ticket Created by Geoffrey Broadwell
> # Please include the string: [perl #53034]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=53034 >
>
>
> The attached small p
HaloO John,
your inquiry rate is quite high. I try to keep-up as good
as I can. Without being authoritative, of course.
you wrote:
If a function returns different things if called in list context or
item context, how do you define the "of" type (outer return type) to
make the function strongly
On Fri Apr 18 04:45:47 2008, doughera wrote:
>
> Debian-derived systems usually offer two packages: A run-time-only
> library and a development library. libreadline5 is the run-time-only
> version. You probably need to do
>
> sudo apt-get install libreadline5-dev
>
> (According to t
I'll consider this patch, but, as all the other code in this module has
corresponding unit tests, we'll have to write a test for it. It should
go in whatever t/configure/*.t file holds other tests for
Parrot::Configure::Options::Test.
kid51
HaloO,
John M. Dlugosz wrote:
sub (::Type $x) # declares generic type parameter as actual type
# of $x argument
sub (::Type $) # ditto, but don't care what the value is. Value
# passed though.
OK.
sub (::Type) # the parameter is a type
On Thu, 17 Apr 2008, James Keenan via RT wrote:
> On Thu Apr 17 10:51:10 2008, ambs wrote:
> > A solution was implemented at revision 27020.
> > They might be cases where this doesn't work. (hope not)
>
> This is what I got on Linux at r27021:
>
> Determining if your platform supports readline..
HaloO,
John M. Dlugosz wrote:
But Newname is not declared yet!
No, but that is the same as with other sigiled terms.
You can also do funny things like
::*Num ::= Complex;
The spec doesn't define namespaces to be protected in any
way. The above is naturally limited to the compile run,
thoug
If a function returns different things if called in list context or item
context, how do you define the "of" type (outer return type) to make the
function strongly typed?
The current intent in the Synopses is that using the :: sigil in a
declaration makes it a generic type parameter and declares that name there.
As a minimal fix to make that work, refine it to say that use of :: as a
sigil in a declaration on a name that contains only a single identifier
(no ::
HaloO,
John M. Dlugosz wrote:
OK, what is the proper use of ::?CLASS ? Say in a role you want to
take an argument of the same class as the final class, or explicitly
declare $self. S12 gives an example:
method doit (::?CLASS $self: $a, $b, $c) { ... }
but this CONTRADICTS the idea that usin
# New Ticket Created by Geoffrey Broadwell
# Please include the string: [perl #53034]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53034 >
The attached small patch makes Configure give a sensible error message
when a conf
32 matches
Mail list logo
