Aaron Sherman writes:
> The question I have is: how do classes control their conversion? In C++
> you can overload the casting operator for any time and/or define a
> constructor for the receiving type.
>
> I can imagine how you would define the constructor on the receiving type
> in Perl 6, but t
Aaron Sherman wrote:
I can imagine how you would define the constructor on the receiving type
in Perl 6, but there's no "casting" syntax in Perl 6. Should we pretend
there is for purposes of defining a conversion and allow:
class foo {
...
sub prefix:IO::Sock
Friday, May 14, 2004, 11:48:00 PM, Andy Dougherty wrote:
>> IMHO, we are currently talking C only, so that shouldn't be a problem. I
>> hope anybody tells me if I'm wrong.
>> Still, I am curious. Why would the linker need to know about C or C++?
> I thought ICU contained some C++ files. As to
On Fri, 2004-05-14 at 10:48, Austin Hastings wrote:
> > my int $i = ...;
>
> Right. This goes back to the notion that lowercase basic types (int,
> str, bool) are "storage efficient" and therefore cannot contain values
> outside the domain, like C.
Nope, not at all.
You can say:
my int
On Thu, 2004-05-13 at 15:35, Dov Wasserman wrote:
> [Special Property #1]
> If the Yada operator is valid anywhere a term is expected, it must
> syntactically valid in all these cases:
>
> my $id = ...;
Since I presume C<...> is going to be of type "Object" or whatever the
universal base class w
On Fri, 14 May 2004 09:11:32 +0200, Bernhard Schmalhofer wrote:
> I have little expertise in building libraries on many platforms. But
> aren't these issues all addressed by GNU's 'libtool'. Is there a
> licensing reason for not using that?
autoconf, automake and libtool address the issues we a
On Thu, 13 May 2004 17:23:18 -0700, Jeff Clites wrote:
>> xxx_STATIC_BUILDcflags and ldflags to build static parrot
> We should make it clear that we are talking about building a static lib
> (to distinguish from what the next macro is intended for)--so how
> about:
> xxx_STATIC_LIB_BUILD or
On Thu, 13 May 2004 10:00:53 -0400 (EDT), Andrew Dougherty wrote:
> You might want to review the patch I submitted about a year and a half ago
> -- it's # 18319, and it included some (but certainly not all) of your good
> ideas.
Thanks, I'll do that.
> I gather parrot's now trying to include stu
Some tests are failing, and there are still issues with
parrotobject-derived thigns, but the changes are all in and should be
a matter of getting the busted stuff un-busted.
--
Dan
--"it's like this"---
D
At 10:48 AM -0700 5/14/04, Jeff Clites wrote:
On May 14, 2004, at 9:04 AM, Dan Sugalski wrote:
Today's project is to get all the MMD things actually using MMD.
I've put in the first wave of changes (well, OK, second if you
consider Leo's BXOR test as the first) and should get the rest of
the stu
On Fri, May 14, 2004 at 10:56:52AM -0700, Austin Hastings wrote:
: It's still invalid to try to fill an lctype with Yadda because of the
: domain issue, right?
That's correct. It would in theory be possible to store a "defined"
bit off to the side somewhere, but that pretty much defeats the purpo
--- Larry Wall <[EMAIL PROTECTED]> wrote:
> On Fri, May 14, 2004 at 07:48:52AM -0700, Austin Hastings wrote:
> : I've argued in the past that it should be possible to put undef
> : into lctypes, to no avail. So, since no "special" values can go
> : into lctypes, I presume this applies to Yadda as
On May 14, 2004, at 9:04 AM, Dan Sugalski wrote:
Today's project is to get all the MMD things actually using MMD. I've
put in the first wave of changes (well, OK, second if you consider
Leo's BXOR test as the first) and should get the rest of the stuff in
today.
This part's a bit hackish but, w
Jim Cromie wrote:
> Jim Cromie wrote:
>
> > folks,
> >
> > attached patch has following adjustments to B::Concise and its tests.
>
>
> heres 2nd rev of that patch, now against 22802
Thanks, applied as change 22820. Time to play with it...
Austin Hastings wrote:
Maybe this is how they'll teach perl at religious schools:
#! /usr/bin/perl6 -w
#
# TEMPLATE.P6 -- standard template for programs at Abstemious U.
#
use no ...;
sub usage() {...}
sub main() {...}
Aha, this is where the DWIM::AI module I suggested on 01-Apr comes
> Austin Hastings wrote:
> >my int $i = ...; # Fails at compile time -- no good conversion.
> >
> >my Int $i = ...; # Warns at compile time, fails at runtime.
>
> I don't get the reasoning here. If Yada Yada Yada is to indicate code
> that you haven't written yet, it should never fail a
On Fri, May 14, 2004 at 07:48:52AM -0700, Austin Hastings wrote:
:
: --- Matthew Walton <[EMAIL PROTECTED]> wrote:
: > I don't get the reasoning here. If Yada Yada Yada is to indicate
: > code that you haven't written yet, it should never fail at compile
: > time unless it's impossible to compile
Today's project is to get all the MMD things actually using MMD. I've
put in the first wave of changes (well, OK, second if you consider
Leo's BXOR test as the first) and should get the rest of the stuff in
today.
This part's a bit hackish but, well, there you go. It does break some
of the obj
[EMAIL PROTECTED] wrote:
Austin Hastings wrote:
my int $i = ...; # Fails at compile time -- no good conversion.
my Int $i = ...; # Warns at compile time, fails at runtime.
I don't get the reasoning here. If Yada Yada Yada is to indicate code
that you haven't written yet, it should never fail
Hi,
whats the plan WRT to CALL__BUILD?
I've written a patch that makes it the default, but does a fallback to
"__init" if no BUILD property is set. If the __init method does not exists,
no exception is thrown (like before), whereas now an exception is thrown if
you specify a BUILD property and
Sorry for the broken reply, but my webmailer makes my life difficult.
--- Matthew Walton <[EMAIL PROTECTED]> wrote:
> Might be nice to have a small checker that you can use on production
=== message truncated ===
Yes. Of course, I fully expect that according to the principle of
maximal surprise,
--- Matthew Walton <[EMAIL PROTECTED]> wrote:
> I don't get the reasoning here. If Yada Yada Yada is to indicate
> code that you haven't written yet, it should never fail at compile
> time unless it's impossible to compile the program without knowing
> what that code is, so
>
> my int $i = ...;
Austin Hastings wrote:
I think of this as very much like the typed-undef we discussed last
month or so: ... should return an unthrown exception wrapped in
undef-ness.
The type returned by ... should just have a multitude of type-casting
tricks associated:
my int $i = ...; # Fails at compile ti
--- Matthew Walton <[EMAIL PROTECTED]> wrote:
> Dov Wasserman wrote:
>
> > my $id = ...;
> > my Int age = ...;
> > my Str $name = ...;
> > my DbHandle $db = ...;
> > my Int of Hash @array = ...;
> >
> > Therefore, the compile-time type of the term must be
> > assignment-compatible with any and a
At 8:58 AM -0400 5/13/04, Sterling Hughes wrote:
patch attached. gist: "how do i manage a simple case of lexical pads?"
Applied. Now to get the darned things answered...
--
Dan
--"it's like this"---
Dan Sug
On Fri, 2004-05-14 at 06:27, Rachwal Waldemar-AWR001 wrote:
> It seems the name 'event' is not as bad. So, maybe 'Pevent', stands for 'parrot
> event'?
> One advantage... it'd be easy searchable. I recall a pain whenever I searched for
> 'thread', or 'Icon'.
If you're talking about search engine
Butler, Gerald wrote:
> How about: "tocsin"
[...thinking out loud...]
I'm not sure it's a good idea to use an obscure word, even if it is
appropriate to the usage. It should be a word that the average user
would recognise, and hopefully be able to intuit some sense of what it
does.
How about "P
I LOVE IT: "PARrot Container for Event Lobbing!!!"
-Original Message-
From: Andy Wardley [mailto:[EMAIL PROTECTED]
Sent: Friday, May 14, 2004 7:36 AM
To: Butler, Gerald
Cc: 'Gordon Henriksen'; '[EMAIL PROTECTED]';
'[EMAIL PROTECTED]'
Subject: Re: Events (I think we need a new name) - Parce
It seems the name 'event' is not as bad. So, maybe 'Pevent', stands for 'parrot event'?
One advantage... it'd be easy searchable. I recall a pain whenever I searched for
'thread', or 'Icon'.
Regards,
Waldemar
-Original Message-
From: Dan Sugalski [mailto:[EMAIL PROTECTED]
Sent: Wednesday
I actually find myself having somewhat coherent thoughts on this matter.
Apologies if they seem rather obvious or naive, but I'm still new to all
this.
Dov Wasserman wrote:
my $id = ...;
my Int age = ...;
my Str $name = ...;
my DbHandle $db = ...;
my Int of Hash @array = ...;
Therefore, the comp
How about: "tocsin"
toc.sin( P ) Pronunciation Key (tksn)
n.
An alarm sounded on a bell.
A bell used to sound an alarm.
A warning; an omen.
-Original Message-
From: Gordon Henriksen [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 13, 2004 2:52 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL
"Larry Wall" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> : does that mean that this use of yada yada yada is already decided on and
allowed?
>
> Yes, with the proviso that it only works that way where a term is
> expected. (As a postfix operator it's short for C<..Inf>.)
So, C<.
On Wed, May 12, 2004 at 06:15:54PM +0200, K Stol wrote:
| >It does, though, sound like we might want an alternate name for this
| >stuff. While event is the right thing in some places it isn't in
| >others (like the whole attribute/property mess) we may be well-served
| >choosing another name. I
On Tue, May 11, 2004 at 02:06:51PM -0400, Dan Sugalski wrote:
> At 1:10 PM -0400 5/11/04, Uri Guttman wrote:
>
> >i don't think there is a need for all those variants. why would alarm
> >need any special opcode when it is just a timer with a delay of abs_time
> >- NOW? let the coder handle that an
On Wed, 12 May 2004, Ron Blaschke wrote:
> I have finally sorted out the details of the flags stuff, which I will
> present below. Any comments are highly appreciated. Be warned: I am going
> to implements this if there are no objections. ;-)
You might want to review the patch I submitted about
patch attached. gist: "how do i manage a simple case of lexical pads?"
cfaq.diff
Description: Binary data
-sterling
Dan Sugalski wrote:
At 5:23 PM -0700 5/13/04, Jeff Clites wrote:
[Most commentary snipped, as it's dead-on]
- When building / using a shared parrot the compiler macro
PARROT_LIB_DYNAMIC will be defined, for static PARROT_LIB_STATIC
What will these be used for? Traditionally, there aren't compile-t
37 matches
Mail list logo
