i have an opportunity to get an email sent to the faculty of a top CS
dept. my goal is to get internal support for a potential YAPC to be
hosted there. so i want to present perl 6 to them in a way which will
sell them on its academic and cutting edge aspects. your mission is to
write some short (2
Hi all,
Some weeks ago, I announced my plans for writing a paper on the
archtecture of Parrot. In the mean time, I made a start, and more or
less defined the structure of the article. It's an initial draft, so
nothing definite yet. Also, as it's a really early draft, not much too
read. Howeve
On Mon, Oct 17, 2005 at 09:18:05PM -0700, Mark A. Biggar wrote:
>
> >Has any FOSS developer ever been found liable (or even sued)?
> >
> >Not that I have any objections to this plan but it might be worth
> >considering that it's much easier to sue a single entity then it is to
> >file a tort again
At 07:03 17/10/2005 -0700, you wrote:
"François PERRAD (via RT)" <[EMAIL PROTECTED]> wrote:
>
> $ ./parrot -V
> This is parrot version 0.3.0-devel (r9493) built for i386-linux.
>
> $ make hello
> ./parrot -o examples/assembly/hello.o examples/assembly/hello.pbc
> make EXEC=examples/assembly/he
Joshua Hoblitt via RT wrote:
> On Sat, Oct 15, 2005 at 11:09:38AM +0300, Jarkko Hietaniemi wrote:
>
>>Joshua Hoblitt via RT wrote:
>>
>>>According to our records, your request regarding
>>> "[BUG] Parrot 0.3.0 t/pmc/io.t assert core dump"
>>>has been resolved.
>>
>>According to my records, it'
Hi all,
Some weeks ago, I announced my plans for writing a paper on the
archtecture of Parrot. In the mean time, I made a start, and more or
less defined the structure of the article. It's an initial draft, so
nothing definite yet. Also, as it's a really early draft, not much too
read. Howeve
# New Ticket Created by Alberto Simoes
# Please include the string: [perl #37463]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37463 >
---
osname= darwin
osvers= 8.0
arch= darwin-thread-multi-2level
cc= cc
---
Fla
I've just added a subrule to PGE,
which is roughly analogous to the "bracketed" function in
Perl 5's Text::Balanced.
Like most PGE subrules, PGE::Text::bracketed can be called
as a subrule in a rule expression or directly via a subroutine call.
Thus, to extract quote-delimited text from a stri
On Sat, Oct 15, 2005 at 08:33:26AM +0300, Markus Laire wrote:
> Could it be possible to create a "Standard library" for perl6, which
> would also include graphical primitives (putpixel, getpixel,
> getcolordepth, putimage, getimage, copyrectangle)?
I'm interested in creating a perl6 binding to c
On Wed, Sep 28, 2005 at 11:46:37AM -0500, Adam D. Lopresto wrote:
> [2] I've actually seen data lost due to this. When drive space is very
> limited
> (due to, for instance, a user quota) it's often possible to open a new file
> (since
> there's some space left), but the close fails since too m
# New Ticket Created by Alberto Simoes
# Please include the string: [perl #37462]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37462 >
Sorry for sending the details this way, but to reorganizing these emails
would take
On Oct 18, 2005, at 19:40, Klaas-Jan Stol wrote:
http://members.home.nl/joeijoei/parrot/paper.pdf
* Strings - we don't have a language field in strings.
Language-specific behavior will depend on the 'environment' of string
usage.
Thanks for your attention,
klaas-jan
leo
Jarkko Hietaniemi wrote:
Joshua Hoblitt via RT wrote:
It's a test failure for unimplemented feature(s). There is already a
TODO ticket (bug #31178) that ruffly covers this. Can you make a case
for why it needs to be to tracked as a software defect?
A core dump is a software defect, an unac
On Tue, Oct 18, 2005 at 11:06:22AM +0100, Nicholas Clark wrote:
> Likewise. A certain reputable OS vendor's NFS implementation went
> multithreaded, with the result that close() was now where the over quota
> error was reported, rather than the individual writes.
>
> Said reputable OS vendor's own
For starters, it gives you a libparrot which doesn't have any external
dependencies. Much nicer, if only aesthetically.
Nick
On 10/18/05, Joshua Hoblitt via RT <[EMAIL PROTECTED]> wrote:
> Chip,
>
> Looks like a design call.
[EMAIL PROTECTED] (Eric) writes:
>> 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.
> Actually its been fixed already. Of course i think the
Disclaimer: I don't ~~ @larry :)
[EMAIL PROTECTED] wrote:
class Bar {
our $.bar;
{
my $.foo;
}
}
I assume that the leading "$." is what makes the difference, however,
IIRC the "$." is just part of the name, and no more special than
that. Which means that I can choose th
Alberto Simoes (via RT) wrote:
Sorry for sending the details this way, but to reorganizing these emails
would take too much time :)
[ Please don't top-post and cite only necessary parts during a f'up. ]
I've checked in a change (r9507) that hopefully fixes this bug (libgdbm
was loaded twice)
Uri,
Well, aside from what is actually *in* Perl 6 currently, there are a
number of interesting side projects, which may or may not get
included in the final language design. Such as:
On Oct 18, 2005, at 3:40 AM, Uri Guttman wrote:
the new OO design (stole the best from the rest and pe
Nick Glencross wrote:
Let me try reposting the patch, which gives me the opportunity to bit
twiddle a bit more:
* Removed the mmap nonsense which was sent by accident
* Renamed config.c to config_string.c to make it less generic
* Moved a couple externs from a core parrot library into th
Some other features:
1) You can write your program in any combination of programming styles
and languages, as you see fit. Thus, you can use your OO library
written in Ruby, that really fast C routine, and your Perl code, all
in one place.
2) There are a large number of operators that support list
On Oct 18, 2005, at 6:56 AM, Miroslav Silovic wrote:
Disclaimer: I don't ~~ @larry :)
[EMAIL PROTECTED] wrote:
class Bar {
our $.bar;
{
my $.foo;
}
}
I assume that the leading "$." is what makes the difference,
however, IIRC the "$." is just part of the name, and no mor
Stevan Little skribis 2005-10-18 10:16 (-0400):
> You are probably right, but are the twigils actually special? or is
> it just a naming convention.
dot sigils are not actually special. They are required on has-variables
and forbidden on all other. Changing them to be optional is trivial, or
so
On Mon, Oct 17, 2005 at 10:09:22PM -0400, Jeff Horwitz wrote:
> On Mon, 17 Oct 2005, Chip Salzenberg wrote:
> > Any problems here? Any suggestions for UUID code that's licensed
> > appropriately for use in Parrot?
>
> the UUID library in e2fsprogs might be appropriate. e2fsprogs is GPL, but
> li
On Tue, 18 Oct 2005, Chip Salzenberg wrote:
> On Mon, Oct 17, 2005 at 10:09:22PM -0400, Jeff Horwitz wrote:
> > On Mon, 17 Oct 2005, Chip Salzenberg wrote:
> > > Any problems here? Any suggestions for UUID code that's licensed
> > > appropriately for use in Parrot?
> >
> > the UUID library in e2f
On Tue, 2005-10-18 at 10:16 -0400, Stevan Little wrote:
> On Oct 18, 2005, at 6:56 AM, Miroslav Silovic wrote:
> > Uhm. I'm not sure either. :) The way I read Larry's mail,
> > multimethods use .isa operator to detect whether $foo belongs to
> > Foo. And for every class, Foo.isa(Foo) is true
I have a suggestion/proposal/whatever.
I am just starting to get a grasp of uses for pairs and where they are
handy. Working on string.trans some showed that it would be useful to have
the function accept a list of pairs. That was working until the fix for
magical pairs went through and now the pa
Allison Randal wrote:
>
> Yes, and in fact we won't be doing copyright *transfers* at all.
> When you sign the contributor agreement, you'll be signing a
> copyright *license*, which still leaves you with the right to
> use the code elsewhere. TPF holds the "compilation copyright",
> that is the co
Leopold Toetsch wrote:
Nick Glencross wrote:
Let me try reposting the patch, which gives me the opportunity to bit
twiddle a bit more:
* Removed the mmap nonsense which was sent by accident
* Renamed config.c to config_string.c to make it less generic
* Moved a couple externs from a c
On Tue, 18 Oct 2005, Chip Salzenberg wrote:
> On Tue, Oct 18, 2005 at 11:27:16AM -0400, Jeff Horwitz wrote:
> > On Tue, 18 Oct 2005, Chip Salzenberg wrote:
> > > On the other hand, the idea has been raised on IRC (by Joshua, IIRC)
> > > that an MD5 or SHA256 would protect against corruption, and w
On Tue, Oct 18, 2005 at 11:27:16AM -0400, Jeff Horwitz wrote:
> On Tue, 18 Oct 2005, Chip Salzenberg wrote:
> > On the other hand, the idea has been raised on IRC (by Joshua, IIRC)
> > that an MD5 or SHA256 would protect against corruption, and would also
> > incidentally make a dandy UUID.
>
> wa
On Oct 18, 2005, at 18:10, Nick Glencross wrote:
Leopold Toetsch wrote:
./miniparrot config_lib.pasm > runtime/parrot/include/config.fpmc
make: *** [runtime/parrot/include/config.fpmc] Error 139
Please check the patch, thanks.
As for the second more serious issue, that's very odd! I assu
[EMAIL PROTECTED] wrote:
U... I'm not sure that allowing $. injection from the nested
blocks is a good thing. I don't think it's ambiguous, but to me it
looks weird and confusing - if a user put the variable in the nested
block like that, it's almost certain he actually meant to write
On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
> 3) Macros. Nuff said.
Not quite. Lispish macros, that is, macros that let you look at what
you're expanding.
> 4) More declarative syntax. This is more of a handwavy, but the syntax
> feels (to me) as if it's more declarative than before. For
On 10/18/05, Uri Guttman <[EMAIL PROTECTED]> wrote:
> i have an opportunity to get an email sent to the faculty of a top CS
> dept. my goal is to get internal support for a potential YAPC to be
> hosted there. so i want to present perl 6 to them in a way which will
> sell them on its academic and c
On 10/18/05, Eric <[EMAIL PROTECTED]> wrote:
> Currently we (can|will be able to) do
>
> "string".trans( (['h','e'] => "0") );
> "string".trans( <== ['h','e'] => "0");
>
> Those are fine and i can live with that, but it seems that if we made the
> signature of trans
>
> method trans(Str $self: [EMA
Luke Palmer skribis 2005-10-18 11:57 (-0600):
> It looks nicer if you use the indirect object form:
> trans "string": [
> => "0",
> ];
It'd also look very nice with optional parens:
"string".trans [ => "0" ];
Or is it not yet time to resuggest that? :)
Juerd
--
http://co
Markus Laire wrote:
I'm not completely sure if it would be worth the trouble to support only
most primitive graphical commands "in core", (no windows, etc..), and
leave the rest to the modules (or to the programmer).
To a large extent, I'd want to leave most details to modules, etc. But
what
JoelOnSoftware wrote an article I recently saw linked on perlmonks:
http://www.joelonsoftware.com/articles/Wrong.html
The article discusses writing robust software, specifically by
dealing with data separation.
In my interpretation the article introduces a type system. This type
system h
On 10/18/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
>
> Uh, no. Certainly not for a method. For a bare sub that has been
> predeclared it may be possible. But we don't want to remagicalize
> pairs after we just argued the heck out of it to make pairs *always*
> be named parameters.
My thought was
On Oct 18, 2005, at 1:45 PM, Luke Palmer wrote:
On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
3) Macros. Nuff said.
Not quite. Lispish macros, that is, macros that let you look at what
you're expanding.
To further expand on this, they will be AST-manipulating macros (LISP
style)
Yuval Kogman skribis 2005-10-18 20:38 (+0200):
> the function encode has the type Unsafe -> Safe
I read the article before. What occurred to me then did so again now.
What exactly do Unsafe and Safe mean? Safe for *what*?
Something that is safe to put in HTML may be unsafe to put in an rfc8
On Tue, Oct 18, 2005 at 21:04:02 +0200, Juerd wrote:
> Yuval Kogman skribis 2005-10-18 20:38 (+0200):
> > the function encode has the type Unsafe -> Safe
>
> I read the article before. What occurred to me then did so again now.
> What exactly do Unsafe and Safe mean? Safe for *what*?
That was
Yuval Kogman skribis 2005-10-18 21:22 (+0200):
> > I read the article before. What occurred to me then did so again now.
> > What exactly do Unsafe and Safe mean? Safe for *what*?
> That was just a naive example - the words "Unsafe" and "Safe" are
> user defined, and are chosen on a case by case ba
On Tue, Oct 18, 2005 at 12:13:33PM -0400, Jeff Horwitz wrote:
> On Tue, 18 Oct 2005, Chip Salzenberg wrote:
> > As for the pbc file case: If you're making a pbc so large that hash
> > creation takes noticeable time, then just imagine how long _writing_
> > it will take? :-)
>
> this answers my qu
Allison Randal wrote:
>
> So, with Perl 5, Larry is the compilation owner. The problem with that
> is it makes Larry personally liable for any action brought against
> Perl (not that that would ever happen, we hope), and a successful suit
> could take his house, his car, his savings, etc. (not t
[snip]
Let me rephrase to see if I understand you - you like the fact that
boxed types + roles applied to those types + compile-time type
checking/inference allows you to tag a piece of information (int,
char, string, obj, whatever) with arbitrary metadata. Add that to the
fact that you can lexica
Sorry if I'm asking a question that I've missed in a synopsis.
Perl 6 will be able to load more than one version of the "same" module.
As I understand it, this would let you have more than one version of
"DBI" loaded in the same interpreter, and also have DBI written by Tim Bunce
and "DBI" written
Nicholas Clark skribis 2005-10-18 22:41 (+0100):
> my $foo = DBI(1.38)->new();
> my $bar = DBI(1.40)->new();
I like this syntax, and have a somewhat relevant question: can a module
be aliased entirely, including all its subclasses/-roles/-.*?
Something like
use DBI as RealDBI;
use
> "SL" == Stevan Little <[EMAIL PROTECTED]> writes:
SL> On Oct 18, 2005, at 1:45 PM, Luke Palmer wrote:
>> On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
>>
>>> 3) Macros. Nuff said.
>>>
>>
>> Not quite. Lispish macros, that is, macros that let you look at what
>> you'
Hi,
Having observed that doing a thesis related to Parrot is trendy (hey,
Klaas-Jan!), I'm now adding to the statistic. :-)
For the next several months, I'm going to be working on translating .NET
bytecode and meta-data into PIR. The end result should mean that you can
load in a .NET class
On 10/18/05, Juerd <[EMAIL PROTECTED]> wrote:
> Nicholas Clark skribis 2005-10-18 22:41 (+0100):
> > my $foo = DBI(1.38)->new();
> > my $bar = DBI(1.40)->new();
>
> I like this syntax, and have a somewhat relevant question: can a module
> be aliased entirely, including all its subclasses/-roles
On 10/18/05, Uri Guttman <[EMAIL PROTECTED]> wrote:
> > "SL" == Stevan Little <[EMAIL PROTECTED]> writes:
>
> SL> On Oct 18, 2005, at 1:45 PM, Luke Palmer wrote:
>
> >> On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
> >>
> >>> 3) Macros. Nuff said.
> >>>
> >>
> >> Not quite.
Nicholas,
This is addressed in S11, here is a link:
http://search.cpan.org/~ingy/Perl6-Bible/lib/Perl6/Bible/S11.pod
To summarize, the syntax to load the modules is:
use Dog-1.2.1;
While the syntax to create a specific version of a module is:
my Dog-1.3.4-cpan:JRANDOM $spot .= new("woo
On Oct 19, 2005, at 0:16, Jonathan Worthington wrote:
Hi,
For the next several months, I'm going to be working on translating
.NET bytecode and meta-data into PIR
... Yay!
Yay2 - one VM to rule them all ...
Jonathan
leo
This is because Parrot is implemented in C,
while developing a large program such as this could well
have been done in C++. This is for three reasons:
1. C is available everywhere
2. there is a large pool of C programmers
3. other languages are not fast enough
I thin
On Tue, Oct 18, 2005 at 21:43:57 +0200, Juerd wrote:
> > That was just a naive example - the words "Unsafe" and "Safe" are
> > user defined, and are chosen on a case by case basis in their app.
>
> I think there's a lot to be gained by implementing something like this
> globally, consistently. CPA
On Wed, Oct 19, 2005 at 02:48:05 +0200, Yuval Kogman wrote:
> the Serializable role, which is an interface spec jointly maintained
Err, I meant the Serializer role... The Serializable role is a role
that takes a delegate that does Serializer, and lets the object that
does it be frozen and thawed.
On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
> On 10/18/05, Uri Guttman <[EMAIL PROTECTED]> wrote:
> > my impression is that both styles are supported as you can return either
> > text or an AST (compiled code) from a macro.
>
> That sounds really ... inefficient. For that to work, you'd have
On Mon, Oct 17, 2005 at 04:16:01AM -0700, Joshua Hoblitt wrote:
> # New Ticket Created by Joshua Hoblitt
> # Please include the string: [perl #37458]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=37458 >
>
>
> This tr
On Tue, Oct 18, 2005 at 04:54:57PM -1000, Joshua Hoblitt wrote:
> On Mon, Oct 17, 2005 at 04:16:01AM -0700, Joshua Hoblitt wrote:
> > # New Ticket Created by Joshua Hoblitt
> > # Please include the string: [perl #37458]
> > # in the subject line of all future correspondence about this issue.
>
> Another school of thought would be that "Dog" alone would be
> considered ambiguious and so we would just alias far enough to be
> clear, like this:
>
>Dog => Ambiguity Error!
>Dog-1.2.1 => Dog-1.2.1-cpan:JRANDOM
>Dog-0.0.2 => Dog-0.0.2-cpan:LWALL
>
> Of course, this means that
On Oct 18, 2005, at 11:15 PM, Rob Kinyon wrote:
NB: Dog-*-cpan:LWALL and Dog-*-cpan:JRANDOM, as well as *-*-cpan:LWALL
are also needed for entry into the mix because if there's only one
module loaded that is signed by cpan:LWALL, that should be sufficient
disambiguation for the parser. (How main
63 matches
Mail list logo
