Richard Hainsworth <[EMAIL PROTECTED]> writes:
>>Steffen said:
>>Maybe an additional
>> use perl5:Wx::SimpleApp;
> Tried it. Doesnt work.
In the meantime I tried my guess and also had to learn that. See also
my experiments in my other answer.
> *However, surely a perl6 program using a perl5 mod
Hello,
Does anyone know if programming languages are protected by copyright or not?
When creating a new program, you are not allowed to pick-and-choose
what you want from other programs sources as that would be a copyright
violation.
But when creating a new programming language, it seems that ev
Markus Laire writes:
> Does anyone know if programming languages are protected by copyright
> or not?
Code can be copyrighted; ideas can't be.
> When creating a new program, you are not allowed to pick-and-choose
> what you want from other programs sources as that would be a copyright
> violatio
HaloO,
Larry Wall wrote:
> I now think it's a bad idea to overload | or & to do type construction,
Is it then a god idea to overload the set operations? At least the
type constructions are set theoretic on the intension set of the
roles.
> especially since the tendency is to define them backwar
HaloO,
Jonathan Lang wrote:
> OK. My main dog in this race is the idea of defining new roles
> through the concepts of the intersection or difference between
> existing roles (even the union was thrown in there mainly for the sake
> of completion), with the consequent extension of the type system
On 10/23/06, Smylers <[EMAIL PROTECTED]> wrote:
Markus Laire writes:
> Does anyone know if programming languages are protected by copyright
> or not?
Code can be copyrighted; ideas can't be.
Yes, but the syntax of the programming language is more than just an idea.
Copyright-article[1] at Wi
HaloO,
Jonathan Lang wrote:
> OK. My main dog in this race is the idea of defining new roles
> through the concepts of the intersection or difference between
> existing roles
Note that you should not call these 'intersection type' because
this term is used for the union of role interfaces. That
TSa schreef:
> A(|)B produces a subtype of A and B, and that A(&)B
> produces a supertype
Are you sure? I see "&" as "limiting; sub" and "|" as "enlarging;
super".
To me, "&" is connected to multiplication (and inproduct, statistics,
fuzzy logic), and "|" to addition (and outproduct).
$ perl -w
On Sun, Oct 22, 2006 at 11:38:10PM +0200, Leopold Toetsch wrote:
> Am Sonntag, 22. Oktober 2006 20:56 schrieb Patrick R. Michaud:
>
> > I strongly disagree. I don't think that a subclass should have to
> > be named as a sub-namespace of its parent class.
>
> Namespace and classes are currently t
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to
complete your request.
Please contact the server administrator, [EMAIL PROTECTED] and inform them of
the time the error occurred, and anything you might have done that may have
caused the error.
HaloO,
Ruud H.G. van Tol wrote:
TSa schreef:
A(|)B produces a subtype of A and B, and that A(&)B
produces a supertype
Are you sure?
Very sure ;)
In record subtyping a record is a mapping of labels to types.
In Perl 6 speak this is what a package does. One record type
is a subytpe if it ha
HaloO,
[EMAIL PROTECTED] wrote:
Log:
"does" operator is non-associative according to S03. Leave it that way for now.
[..]
-$fido does Sentry | Tricks | TailChasing | Scratch;
+$fido does (Sentry, Tricks, TailChasing, Scratch);
Does that apply to the trait verbs used in class definitio
On 10/23/06, Markus Laire <[EMAIL PROTECTED]> wrote:
On 10/23/06, Smylers <[EMAIL PROTECTED]> wrote:
> Markus Laire writes:
>
> > Does anyone know if programming languages are protected by copyright
> > or not?
>
> Code can be copyrighted; ideas can't be.
Yes, but the syntax of the programming
TSa writes:
> Ruud H.G. van Tol wrote:
>
> > TSa schreef:
> >
> > > A(|)B produces a subtype of A and B, and that A(&)B produces a
> > > supertype
> >
> > Are you sure?
>
> Very sure ;)
In which case that provides a handy example supporting Larry's
suggestion that this is confusing, with some
HaloO,
Smylers wrote:
In which case that provides a handy example supporting Larry's
suggestion that this is confusing, with some people expecting it to work
exactly opposite to how it does.
So the mere fact that there are two sets involved rules out the
set operators as well?
It doesn't re
Karl Forner wrote:
I've added one C src file, say src/foo.c, and include/parrot/foo.h, and a
test in t/src/foo.t.
I've changed the MANIFEST file accordingly, but I can not manage to
have my
foo.o file to be added in libparrot.a (after a make clean;perl
Configure.pl
;make)
What did I miss ?
No
Smylers wrote:
TSa writes:
> Ruud H.G. van Tol wrote:
> > TSa schreef:
> > > A(|)B produces a subtype of A and B, and that A(&)B produces a
> > > supertype
> >
> > Are you sure?
>
> Very sure ;)
In which case that provides a handy example supporting Larry's
suggestion that this is confusing, wit
HaloO,
Jonathan Lang wrote:
Please, no attempts to merge signatures. Instead, use multiple
dispatch
That avoids the problem before it occurs. But do you expect
every role to provide its methods as multi just in case?
Also, sub is an odd choice to use while illustrating role composition;
wh
Just wanted to collect information about ParrotClass and ParrotObject.
I can't seem to instantiate a ParrotObject from a ParrotClass using the
new opcode.
I've seen references to the instantiate_object opcode but it seems
unimplemented.
I know the object pdd is coming up on Allison's stack,
TSa <[EMAIL PROTECTED]> wrote:
I strongly agree. Having a language that allows supertying has novelty.
But I think that union is not there for completion but as integral part
when it comes to defining a type lattice which I still believe is the
most practical approach to typing. This includes com
Author: jonathan
Date: Mon Oct 23 08:19:59 2006
New Revision: 15000
Modified:
trunk/docs/pdds/clip/pdd13_bytecode.pod
Log:
Add annotation groups to the bytecode specification.
Modified: trunk/docs/pdds/clip/pdd13_bytecode.pod
===
HaloO,
Jonathan Lang wrote:
If we make a point of highlighting the "set operations" perspective
You know that there are two sets involved. So which one do you mean?
and avoiding traditional type theory
terminology (which, as Larry pointed out and TSa demonstrated, is very
much inside out fr
TSa wrote:
Jonathan Lang wrote:
> OK. My main dog in this race is the idea of defining new roles
> through the concepts of the intersection or difference between
> existing roles
Note that you should not call these 'intersection type' because
this term is used for the union of role interfaces.
HaloO,
Jonathan Lang wrote:
BTW, are the ASCII equivalents spelled (<), (>) and (in)?
I'd hope that they'd be something like '(<)', '(>)', and 'in'; only
use parentheses when neccessary. Likewise, I'd want the "relative
complement" operator to be '-', not '(-)'.
Funny. I would have hoped th
Jonathan Lang schreef:
> (&) and (|) would actually reflect your intuition regarding the
> capabilities of the result, in that a role arrived at by means of (&)
> would provide fewer options than the individual roles used to create
> it, while a role arrived at by means of (|) would provide more
>
TSa wrote:
Jonathan Lang wrote:
> Please, no attempts to merge signatures. Instead, use multiple
> dispatch
That avoids the problem before it occurs. But do you expect
every role to provide its methods as multi just in case?
Conceded.
Bear in mind, though, that signatures include not only ty
Author: jonathan
Date: Mon Oct 23 09:30:39 2006
New Revision: 15001
Modified:
trunk/docs/pdds/clip/pdd13_bytecode.pod
Log:
Add dependencies segment to the specification and fix string constants storage.
Modified: trunk/docs/pdds/clip/pdd13_bytecode.pod
Hi,
Sorry for delay in getting to this - been working on-site with $JOB for
a while. Comments and questions below, but please see r15001.
Leopold Toetsch wrote:
2) How should we handle changes to the core Parrot library (mostly PMCs,
but also consider anything we promise is available)? Should
HaloO,
Jonathan Lang wrote:
Bear in mind, though, that signatures include not only type
information, but also parameter names; and method calls are permitted
to pass an argument into a given parameter by means of its name
instead of its position, so the names cannot be disregarded. For
instance
HaloO,
Jonathan Lang wrote:
my @array = (0,1,2); # Array of Int
@array[3] = "three"; # Array of Int(&)Str
Actually, these would be something along the lines of "Array of Int"
and "Array of (Int, Int, Int, Str)", respectively. That is, each of
@array[0..2] would be of type "Int", while @ar
Allison Randal wrote:
I think the object model needs a thorough going over in general
Yup. It's on the list right after I/O, threads, and events.
-- for
the reasons above and because it's an unproven system. I'm not
convinced that it will handle all of Perl 6's needs as is. No serious
OO langu
In languages/lua/lib/thread.pir, I create a Lua thread type by extension of
Parrot::Coroutine.
So I add a lot of methods for Lua type, but I think that 2 of these methods
could be integrated in Parrot::Coroutine :
- __clone
- __get_pointer (equivalent of get_pointer() in src/pmc/sub.pmc)
Fran
On Monday 23 October 2006 09:49, Jonathan Worthington wrote:
> Would it be a good idea to start collecting requirements together from
> different language implementors so that when the time comes to work on
> the OO PDD, there is already a good description of what it needs to do?
> If so, I'm happ
On Mon, Oct 23, 2006 at 05:49:08PM +0100, Jonathan Worthington wrote:
> Allison Randal wrote:
> >>I think the object model needs a thorough going over in general
> >Yup. It's on the list right after I/O, threads, and events.
> >...
> >Ruby is a serious OO language, but it's not finished yet. For t
TSa wrote:
I don't know how close leaving an undefined method as described above
to the class designer comes to automated merge. Note that at no point
I'm arguing that the body be merged. I'm seeing guarantees that the type
system tries to hold up in favour of the users of roles.
If you're not
Am Montag, 23. Oktober 2006 15:14 schrieb Patrick R. Michaud:
> > .HLL 'pge', ''
> > ...
> > cl = newclass 'Exp' # ['pge'; 'Exp']
> > ...
> > .namespace ['Exp'] # ['pge'; 'Exp']
> > ...
> > scl = subclass 'Exp', ['Exp'; 'Closure'] # ['pge'; 'Exp'; 'Closure']
> > ...
>
> It
Am Montag, 23. Oktober 2006 16:58 schrieb Kevin Tew:
> I can't seem to instantiate a ParrotObject from a ParrotClass using the
> new opcode.
You have a code snippet? Did you have a look at t/pmc/obj*.t or all the tons
of OO usage all over libs?
leo
Am Montag, 23. Oktober 2006 18:31 schrieb Jonathan Worthington:
> > 1,5) same + range of indices
> >
>
> Will a dynamic character set or encoding library that we load not
> possibly contain more than one character set or encoding and therefore
> need a range of indices too? I have gone with thi
> This patch adds a test for DOS line endings in text files in the
> Parrot distribution.
>
> Comments welcome,
Hi Paul,
could you add a check for SVN::Client and skip the test when there is no
SVN::Client?
Bernhard,
No worries :-) Please see attached patch.
I noticed something odd when I w
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Tue Oct 24 04:08:49 2006 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
On Oct 23, 2006, at 7:39 AM, Paul Cochrane wrote:
BEGIN {
eval { use SVN::Client; };
if ($@) {
plan skip_all => 'SVN::Client not installed';
}
}
Paul,
This should be
eval {require SVN::Client; };
use() is a compile-time directive, not runtime.
Chris
--
Chris Dolan, S
I suppose the reason it's more efficient is that it compiles it at actual
compile time. The only use I know of eval{} is catching dies...
On 10/23/06, Paul Cochrane <[EMAIL PROTECTED]> wrote:
> > This patch adds a test for DOS line endings in text files in the
> > Parrot distribution.
> >
> > C
On October 16th Damian Conway wrote:
> If the contents are not a number, they are interpreted as an upper-case
> Unicode character name, or as a lower-case XHTML entity. For example:
One more problem: not all XHTML entities are lower-case. For example:
Ð Þ É Θ
For a complete list, see:
ht
43 matches
Mail list logo
