John M. Dlugosz 提到:
What is the difference between (1,2,3) and [1,2,3] ?
One is a List and one is an Array; you cannot push into a list, but you
can into an array.
my @a := (1,2,3);
my @b := [1,2,3];
@a.push(4); # fails
@b.push(4); # works
Cheers,
Audrey
John M. Dlugosz 提到:
Does that mean that traits can come before the signature? Or should it
be corrected to
method close () is export { ... }
It's a simple typo. Thanks, fixed in r14572.
Cheers,
Audrey
John M. Dlugosz 提到:
I've edited several of the S??.pod files,but I have not heard back from
the owner ($Larry, whose name is on the top of the file) about accepting
merging or rejecting my changes.
I've posted the files to http://www.dlugosz.com/Perl6/offerings/ so
they don't get lost, until
Audrey Tang 提到:
However, in S02 you removed the Code class and replaced it with Routine,
but that does not really work; for example, a bare block is a Code, but
it cannot be a Routine since it can't be wrapped in place, and caller()
would bypass it when considering caller frames.
I should've
John M. Dlugosz wrote:
A method can refer to private attributes etc. in other objects than
self. This is unlike Smalltalk and like C++. Which objects? Obviously,
those that _have_ them in the first place.
Correct, though those classes also has to trust the calling class:
class MyClass { has
John M. Dlugosz wrote:
That seems to be saying that using the method-call form is preferred, as
it abstracts whether it is a real hard attribute or not.
Er, it is not so.
The $.foo notation is good not only for calling accessors, but also as a
way to specify context when calling oneself's
John M. Dlugosz wrote:
OK, trust is not implicit on derived classes. Is that because there is
no rule that says it is, or is there a mention of that somewhere in the
official docs?
There is. S12 Line 561:
Every Idot declaration also declares a corresponding private
Iexclamation storage
John M. Dlugosz 提到:
In S29, there are definitions like
our Capture method shape (@array: ) is export
But in S12 there is no mention as to what an our method is. It states that
my is used to make private methods, and ^ to make class methods.
I think this is a doc relic and should be fixed
John M. Dlugosz 提到:
= on Parallelized parameters and autothreading
use autoindex;
do { @c[$^i, $^j, $^k, $^l] = @a[$^i, $^j] * @b[$^k, $^l] };
Shouldn't those be semicolons? Ditto for subsequent examples.
Also, what does the do do? I think it is only meaningful if there was
Audrey Tang 提到:
John M. Dlugosz 提到:
= on Parallelized parameters and autothreading
use autoindex;
do { @c[$^i, $^j, $^k, $^l] = @a[$^i, $^j] * @b[$^k, $^l] };
Shouldn't those be semicolons? Ditto for subsequent examples.
Also, what does the do do? I think it is only meaningful
John M. Dlugosz 提到:
But about your answer, automatically called with no arguments. Isn't
that what a bare closure normally does anyway? Say, I introduced extra
{} just for scoping or naming the block, where a statement is expected.
foo;
bar;
{ my $temp= foo; bar(temp); } #forget about
John M. Dlugosz 提到:
I just finished another pass on S09v24, and in this posting I note
editorial issues with the file that can easily be corrected. This is as
opposed to subjects for deep discussion, which I'll save for later and
individual posts.
= on Mixing subscripts
Within a C.[]
Larry Wall 提到:
Yes, unless we decide we need something like that for list
comprehensions. Maybe looping modifiers allow placeholders in what
would otherwise be an error...
Sure. How about this:
Use of a placeholder parameter in statement-level blocks triggers a
syntax error, because the
Larry Wall 提到:
I was originally thinking just loop modifiers, but I suppose
{ say $^x } if foo();
also can be made to make some kind of sense, in the same way that
if foo() - $x { say $x }
is supposed to work.
Right. I've committed the clarification (as a new section).
Nicholas Clark 提到:
So if the semicolon is replaced with a comma, like this,
my @x := [{1+1}, {2+2}];
the {} acts as a hash constructor, and @x is [{2 = undef}, {4 = undef}] ?
No, {} acts as a closure constructor, and @x contains two closures that
returns 2 and 4 respectively when
Thom Boyer 提到:
Audrey Tang wrote:
$code = { a = 1, $b, $c == print };
The examples above are from LS04/Statement parsing.
According to those rules, that last assignment to $code seems to be a
hash, not code. Or does the C == mean that the contents aren't a
list?
Correct, because
在 Jun 11, 2007 5:10 AM 時，Jonathan Lang 寫到：
A variation of chaining associativity gets
used, with the chaining rule being '$v1 op1 $v2 // $v1 op2 $v3'
instead of '$v1 op1 $v2 $v2 op2 $v3', as is the case for comparison
chaining.
But wouldn't that make:
True ?? undef !! Moose;
evaluate to
在 May 21, 2007 8:45 AM 時，Juerd Waalboer 寫到：
Steffen Schwigon skribis 2007-05-21 1:28 (+0200):
That's ARRAY := ARRAY there, so the following should dwym:
my @foo := [ 1, 2, 3 ];
However, this does not work with pugs, so I don't know if I am
wrong, or
pugs is wrong.
Pugs is wrong
在 Apr 20, 2007 7:45 PM 時，Agent Zhang 寫到：
On 4/13/07, Agent Zhang [EMAIL PROTECTED] wrote:
Okay, I think I've fixed the bug by defaulting to YAML.pm instead of
YAML::Syck. As confirmed by Ingy++, The current version of YAML::Syck
on CPAN is having problem with single-quotes in its emitter:
在 Feb 26, 2007 3:37 AM 時，Eric Hanchrow (via RT) 寫到：
# New Ticket Created by Eric Hanchrow
# Please include the string: [perl #41617]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41617
Here's what I did:
$ svn co
2007/2/27, Geoffrey Broadwell [EMAIL PROTECTED]:
As a simpler case than a full 3D engine port, I have some OpenGL
benchmarks in Perl 5 that I can port -- these have much reduced
requirements. Principly, they need:
1. Basic math and string operators (not grammars)
2. Basic looping and simple
2007/2/27, Geoffrey Broadwell [EMAIL PROTECTED]:
7. Packed arrays with access to raw data pointer to give to API
Is it possible to point us to some use cases of such packed arrays,
especially the raw data pointer API part?
Are you looking for Perl code that creates such packed arrays and
在 Feb 9, 2007 5:17 AM 時，Larry Wall 寫到：
Questions and feedback welcome, but please don't follow up to this
message--start a new thread for a new topic. Bear in mind that
this is completely untested code, still fairly buggy and incomplete.
Not even pugs can parse it (yet).
Note: After some typo
在 Feb 6, 2007 11:07 PM 時，Gabor Szabo 寫到：
On http://www.pugscode.org/ when I click Download
I get to the wiki on rakudo and (yippi it works again !)
but the link to the Win32 binary builds of Pugs and Parrot
brings me to http://jnthn.net/public_html/perl6/ which is 404.
Fix the rakudo wiki to
在 Dec 18, 2006 5:52 AM 時，Fayland Lam 寫到：
we are trying to translate them into Chinese. so I just wonder
where can I get the .pod source?
http://svn.perl.org/perl6/doc/trunk/design/syn/
Cheers,
Audrey
After a week of planning, and with plenty of help from clkao++, obra+
+, #jifty, #bps and #perl6, I'm glad to announce that Pugs now has a
new, permanent URL for its subversion repository:
http://svn.pugscode.org/pugs/ (HTTP)
https://svn.pugscode.org/pugs/ (HTTPS)
Subversion users,
在 Oct 26, 2006 10:26 AM 時，TSa 寫到：
I figure that
http://svn.openfoundry.org/pugs/docs/notes/multi_method_dispatch/
mmd-draft.txt
hasn't made it into S06 yet. So what is the current state of affairs?
The original plan was to have Larry review it in Brazil and check it
in along with an
在 Oct 29, 2006 4:34 PM 時，Richard Hainsworth 寫到：
If I have the following
my $self = some text;
my $nself = ~eval(q/self is $self/,:langperl5);
then surely $nself should be self is some text.
But it is not. $self is not set inside the eval in pugs.
But
say ~eval(q/self is $self/);
yields
在 Oct 29, 2006 4:34 PM 時，Richard Hainsworth 寫到：
If I have the following
my $self = some text;
my $nself = ~eval(q/self is $self/,:langperl5);
then surely $nself should be self is some text.
But it is not. $self is not set inside the eval in pugs.
The lexical pad is not yet shared with
After nearly four months of development and 3400+ commits, I'm very glad
to announce that Pugs 6.2.13 is now available:
http://pugs.blogs.com/dist/Perl6-Pugs-6.2.13.tar.gz
SIZE: 6839270
SHA1: b06b8434c64e9bb5e3ab482282fbae0a6ba69218
Motivated by increasing use of Pugs in production,
在 Oct 12, 2006 2:39 PM 時，Ovid 寫到：
--To forcefully add a role to a class at a distance during runtime,
use
a class object call (see Moose::Meta::Class for more about these
APIs):
^Dog.add_role(^Catlike);
That's more of what I was thinking, but where is this documented? I
can't find
在 Oct 12, 2006 5:43 AM 時，Tim Bunce 寫到：
On Tue, Oct 10, 2006 at 01:31:59PM -0700, Ovid wrote:
Hi all,
In doing a bit of work with traits (roles) in Perl 5
(http://perlmonks.org/?node_id=577477), I've realized some edge cases
which could be problematic.
First, when a role is applied to a
在 Oct 3, 2006 10:22 PM 時，Wim Vanderbauwhede 寫到：
say (- $n { - $f { $f($n,$f) }.( - $n, $f { $n2 ?? 1 !! $n*$f
($n-1,$f)
}) }).(5);
say OK;
#say (- $n { - $f { $f($n,$f) }.( - $n, $f { $n2 ?? 1 !! $n*$f
($n-1,$f)
}) }).(5);
say OK;
It's extremely subtle -- $n2 should never have parsed in
在 Oct 4, 2006 7:46 AM 時，Damian Conway 寫到：
[Apologies for the last post. Gmail got a little eager.
Here's what I meant to send...]
Juerd wrote:
Which can also be written as:
do { do { say 1 if 1 } if 1 } if 1;
Sorry, no it can't. From S4
(http://dev.perl.org/perl6/doc/design/syn/
在 Oct 4, 2006 10:17 AM 時，Damian Conway 寫到：
Audrey asked:
However, I wonder if this is too strict. Disallowing while and
until after a do block is fine (and can be coded directly in those
two statement modifier macros), but is there a reason to disallow
other modifiers?
Well, for a start,
在 Sep 30, 2006 6:26 PM 時，Richard Hainsworth 寫到：
role win_text {
has $.win_mytxt1 is rw;
has $.win_mytxt2 is rw;
};
role mywindow {
has $.border is rw;
has $.colour is rw;
does win_text;
};
my $w = new mywindow;
$w.border = 2;
$w.colour = 'red';
say $w.border;
say $w.colour;
在 Oct 2, 2006 5:56 PM 時，Audrey Tang 寫到：
At this moment only role mywindow does win_text works; the
statement-level does form was not implemented, but I should be
able to do so in the next few days.
Update: It's now implemented as r13782.
Richard: The t/README file should get you started
在 Sep 28, 2006 3:03 AM 時，Carl Mäsak 寫到：
Audrey ():
Indeed... Though what I'm wondering is, is there a hidden
implementation
cost or design cost of making /foo+/ always behave such that
$foo.from
returns something, compared to the current treatment with the
workaround
you suggested?
Has
在 Sep 22, 2006 10:36 PM 時，Patrick R. Michaud 寫到：
Out of curiosity, why not:
/foo bar bar $xyz:=(foo+)/
and then one can easily look at $xyz.from and $xyz.to, as well
as get to the arrayed elements? (There are other possibilities as
well.)
I'm not arguing in favor of or against the
在 Sep 23, 2006 8:36 PM 時，Markus Laire 寫到：
On 9/23/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
@args = [EMAIL PROTECTED],1,2,3;
-push [,] @args;# same as push @foo,1,2,3
+push [,] @args;# same as push(@foo: 1,2,3)
I don't quite understand this. Shouldn't C[,] @args
在 Sep 24, 2006 12:21 AM 時，Audrey Tang 寫到：
在 Sep 23, 2006 8:36 PM 時，Markus Laire 寫到：
On 9/23/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
@args = [EMAIL PROTECTED],1,2,3;
-push [,] @args;# same as push @foo,1,2,3
+push [,] @args;# same as push(@foo: 1,2,3)
I don't
From S05:
If a subrule appears two (or more) times in any branch of a lexical
scope (i.e. twice within the same subpattern and alternation), or if the
subrule is quantified anywhere within a given scope, then its
corresponding hash entry is always assigned an array of
CMatch objects rather than
在 Sep 4, 2006 2:11 AM 時，Gaal Yahas 寫到：
Unless I'm mistaken, this doesn't cast back to subroutine signature
land
very well:
sub f1 (Dog ($fido, $spot)) { ... }
sub f2 (Dog $ ($fido, $spot)) { ... }
sub f3 (Dog :($fido, $spot)) { ... }
Correct.
Unless Audrey's latest
在 Sep 11, 2006 2:07 PM 時，Trey Harris 寫到：
In a message dated Mon, 11 Sep 2006, Richard Hainsworth writes:
I am trying to find out how to use (in perl6) perl5 modules that
contain subroutines.
Imports from Perl 5 modules don't currently work.
Actually, explicit imports do work (as of a
在 Sep 12, 2006 6:59 PM 時，Gaal Yahas 寫到：
What invocant is constructed in this signature then?
method foo ($just_a_named_param)
Is the signature for foo really the same as that of bar?
sub bar ($just_a_named_param)
As Larry said, they shouldn't be the same; the first one is
2006/9/12, Gaal Yahas [EMAIL PROTECTED]:
Does this mean a single named parameter called $x, or a default invocant
and a single required positional named $x?
A default invocant prolly doesn't make sense there... There's
nothing to default to. :-)
Audrey
Consider these cases:
[=] $x, $y, $z;
[+=] $a, $b, $c;
S03 is currently inconsistent. It first says these are not supported:
The final metaoperator in Perl 6 is the reduction operator. Any
infix operator (except for non-associating operators and assignment
operators) can be surrounded
在 Sep 8, 2006 10:33 PM 時，Michael Snoyman 寫到：
Thanks Audrey. I actually found that after writing that post.
What I had wanted to do was write a threaded server, implemented in
Perl 6 only (ie, including Perl 6 regexs). I got that working
almost entirely, when I couldn't find any thread
在 Aug 25, 2006 12:54 AM 時，Michael Snoyman 寫到：
I was thinking of rewriting a little webserver program I wrote in
Perl 5
using Pugs. I was wondering what the equivilent (if any) of
IO::Socket is.
I suppose I could use an external webserver and use CGI to get this
working
with IO, but my
2006/9/4, Ph. Marek [EMAIL PROTECTED]:
On Sunday 03 September 2006 14:25, Mark Stosberg wrote:
Luke Palmer wrote:
On 9/3/06, Mark Stosberg [EMAIL PROTECTED] wrote:
Note that the variant /with/ the parameter can be considered an exact
match, but but the variant /without/ it cannot be
2006/9/2, Markus Laire [EMAIL PROTECTED]:
I tried to compile pugs r12925 with parrot r14364 (both current as of
yesterday) and make for pugs failed with this message:
Heya. r12925 is at the middle of gaal's mad hax0ring to support
:(Sig) syntax in addition to \(Capt) syntax. Can you try
2006/9/2, Markus Laire [EMAIL PROTECTED]:
On 9/2/06, Audrey Tang [EMAIL PROTECTED] wrote:
2006/9/2, Markus Laire [EMAIL PROTECTED]:
I tried to compile pugs r12925 with parrot r14364 (both current as of
yesterday) and make for pugs failed with this message:
Heya. r12925 is at the middle
2006/9/1, Juerd [EMAIL PROTECTED]:
Luke Palmer skribis 2006-08-31 15:48 (-0600):
I don't think using a method (even if called s) is good huffman
coding. My expectation is that copying substitution will be used much -
perhaps even more than mutating substitution!
And so a method called s
2006/8/26, Mark J. Reed [EMAIL PROTECTED]:
I noticed that tr/// doesn't currently exist in pugs. I want to add a
test, but I'm not sure where it goes. My first instinct is to create
a new tr.t in operators/, but I could also see adding it to builtins,
or even to the trans test in string. So I
2006/8/26, [EMAIL PROTECTED] [EMAIL PROTECTED]:
So what's the rationale behind the latest changes? I thought p6
consistently regarded the sigil as part of the name; seems like that
should go for named parameters, too. In fact, sigils would seem to be
a good way to distinguish named parameters
在 2006/8/25 上午 4:37 時，Larry Wall 寫到：
On Thu, Aug 24, 2006 at 03:11:10PM -0400, Mark J. Reed wrote:
: On 8/24/06, Larry Wall [EMAIL PROTECTED] wrote:
: On Wed, Aug 23, 2006 at 05:01:43PM -0400, Mark J. Reed wrote:
: : Sorry if this is a known question, but I didn't see it
mentioned in the
:
在 2006/8/18 上午 3:31 時，Ben Morrow 寫到：
Just to make sure I've got all this straight:
=:= compares names
=== compares containers
eqv compares values
=:= evaluates both sides as lvalue -- that's VAR() -- and compare
them with ===.
=== evaluates both sides as rvalue and, for
在 2006/8/12 上午 3:01 時，jerry gay 寫到：
for managed, i have a few ideas. currently, the suite lives in the
pugs repo. this is a fine first approximation, but i believe it will
soon be time to move this suite (it doesn't make sense to keep the
official tests in a non-official repo in the long term.)
在 2006/8/12 下午 6:15 時，Nicholas Clark 寫到：
There's nothing technical stopping the Perl 6 tests being on
svn.perl.org,
but in a different svn repository from the current repositories, is
there?
Well, technically yes, except that SVK doesn't support svn:external yet.
Setting a svn:external
在 2006/8/11 下午 2:35 時，Luke Palmer 寫到：
I think that standard functions ought not to have underscores *most of
the time*, because their presence indicates something that could be
better named or is miscategorized. However, for methods, especially
advanced or introspective methods, I think longer
在 2006/8/2 下午 2:48 時，Arthur Ramos Jr. 寫到：
I'm new to the mailing lists. I've just started reading all the
Apocalypse and
Exegeses with the goal of becoming involved in some manner.
Try reading the Synopses first. :-)
The Apocalypses and Exegesis are no longer updated, and has diverged
在 2006/7/28 上午 7:54 時，Aaron Crane 寫到：
The motivation for s/environmental/contextual/ is clear: avoiding a
term
that's already used for something else. But, on the same grounds,
I'm not
sure that contextual is the right term, and especially not Cis
context
-- Perl already has contexts,
在 2006/7/23 上午 7:33 時，Agent Zhang 寫到：
Hello, everyone~
Here's my patch for S03.
Thanks, applied (and the previous one on S02 too)!
Audrey
PGP.sig
Description: This is a digitally signed message part
在 2006/7/19 下午 10:16 時，Agent Zhang 寫到：
I found some nits while copying Perl 6 Synopsis 2 by hand. The patch
created by my TortoiseSVN for S02 has been pasted at the end of the
mail.
Thanks, applied as r10314.
Audrey
PGP.sig
Description: This is a digitally signed message part
在 2006/7/18 上午 1:54 時，Audrey Tang 寫到：
If you have a way to make IMCC reentrant that involves upgrading
to a more recent version of flex and passing one additional
parameter, go for it! Send us a patch and if it passes all the
tests, we'll apply it.
As flex 2.5.30+ is not API compatible
Vishal,
在 2006/7/16 下午 11:57 時，Vishal Soni 寫到：
a. Remove flex and implement re2c
b. Remove static and global variables
Now that the flex part is done, are you still willing to help
removing the remaining static/global state?
Apart from this we also need to refactor the code to get
在 2006/7/18 上午 4:38 時，Allison Randal 寫到：
[EMAIL PROTECTED] wrote:
This is not a maintainable build solution. Revert and come back
when you have one.
Reverted.
Audrey
PGP.sig
Description: This is a digitally signed message part
在 2006/7/18 上午 4:49 時，chromatic 寫到：
I don't believe there's a working heuristic for guessing which
parameter the
user failed to provide. That's why I didn't write the original
version that
way.
Does r13347 look better? If not, please revert both my changes.
As an aside, regardless of
在 2006/7/18 上午 4:38 時，Allison Randal 寫到：
This is not a maintainable build solution. Revert and come back
when you have one.
Please clarify: What, exactly, is not maintainable? The presence of
a .diff file, or the fact that it needs to be applied manually?
If the latter, an extra line of
在 2006/7/18 上午 5:24 時，Audrey Tang 寫到：
在 2006/7/18 上午 4:38 時，Allison Randal 寫到：
This is not a maintainable build solution. Revert and come back
when you have one.
Please clarify: What, exactly, is not maintainable? The presence
of a .diff file, or the fact that it needs to be applied
在 2006/7/18 上午 6:21 時，Audrey Tang 寫到：
在 2006/7/18 上午 5:24 時，Audrey Tang 寫到：
在 2006/7/18 上午 4:38 時，Allison Randal 寫到：
This is not a maintainable build solution. Revert and come back
when you have one.
Please clarify: What, exactly, is not maintainable? The presence
of a .diff file
在 2006/7/18 下午 1:41 時，Chip Salzenberg 寫到：
What versions of flex and bison will work now? I'd like to make
Configure.perl (or perhaps the Makefile at runtime?) choke on --
maintainer
if the right versions aren't found.
Flex 2.5.33, Bison 2.2.
Thanks,
Audrey
PGP.sig
Description: This is
在 2006/7/18 下午 3:55 時，jerry gay 寫到：
On 7/18/06, chromatic [EMAIL PROTECTED] wrote:
On Tuesday 18 July 2006 02:21, Audrey Tang wrote:
Does r13347 look better? If not, please revert both my changes.
I think it's still misleading. #13364 is probably as accurate as
Parrot can
report
在 2006/7/17 下午 3:41 時，Joshua Hoblitt 寫到：
4th Option: fix flex. ;)
Turns out flex 2.5.30+ has a reentrant mode. However, it also has an
incompatible API with earlier flex,
even in non-reentrant mode. I've attached a patch under http://
rt.perl.org/rt3//Public/Bug/Display.html?id=34669
在 2006/7/18 上午 1:21 時，Allison Randal 寫到：
LOL :) Audrey, I love you dear, but you always have an interesting
way of interpreting what I say. :)
Yes, I'm not willing to start a 6+ month project to gut IMCC. The
cost is too great and the benefit isn't great enough.
Indeed, and I'd like to
在 2006/7/16 下午 11:57 時，Vishal Soni 寫到：
a. A clean implementation rather than a prototypish implementation
I think that the lemon+re2c, being the more modern parsing tools,
will make refactoring/hacking considerably easier. Whilst you are
converting the current IMCC implementation into
在 2006/7/14 上午 5:26 時，Leopold Toetsch via RT 寫到：
Err, t/dynpmc/dynlexpad.t is using .loadlib and is testing fine.
Please try to
provide a minimal parrot test showing the problem.
Trying (though it remained a bit elusive), but if you make
realclean, and then change
在 2006/7/14 上午 6:45 時，Audrey Tang 寫到：
Changing it back to :immediate makes tests pass again.
Alternately, skipping the Parrot_register_HLL part in IMCC makes
tests pass again.
After several rounds of trial-and-error, I've committed r13294 that
works around the problem:
* Tcl: Change
在 2006/7/12 下午 9:38 時，Chip Salzenberg 寫到：
On Wed, Jul 12, 2006 at 05:29:08PM -0700, [EMAIL PROTECTED] wrote:
* Apply heuristics that tells
.loadlib 'perl6_group' # HLL dynamic PMCs
and
.loadlib 'dynlexpad'# non-HLL dynamic PMCs
apart, by locating the '_group substring inside
在 2006/7/12 下午 8:16 時，Allison Randal 寫到：
[EMAIL PROTECTED] wrote:
Modified: trunk/languages/perl6/perl6.pir
=
=
--- trunk/languages/perl6/perl6.pir (original)
+++ trunk/languages/perl6/perl6.pir Wed Jul 12
在 2006/7/13 上午 3:35 時，Audrey Tang 寫到：
If Leo's comment about .loadlib being compile-and-runtime is
already implemented, then you should be able to eliminate that
runtime call to the loadlib opcode too.
Indeed, though as I tested it (both at the time of the commit and
at this moment
在 2006/7/11 下午 7:33 時，Chip Salzenberg via RT 寫到：
Now think about the alternatives if your goal is to have the table
ready to
go at runtime without any computational overhead at all, e.g. a CRC
table.
And if we can restrict :immediate using some security principal in
the future so
it can
在 2006/7/11 下午 11:52 時，Bob Rogers via RT 寫到：
But by compile time you both unambiguously mean PIR compile time,
not HLL compile time, since there's no HLL involved. But an HLL
compiler always has the option of building a PIR constant at HLL
compile
time [2], so that just leaves the case of
So far we have been enable to produce a use case that requires
unbounded evaluation
(typo, it's unable above.)
PGP.sig
Description: This is a digitally signed message part
Allison and Chip expressed their go-ahead with a .loadlib pragma, to
replace this current use:
.sub foo :immediate
$I0 = loadlib XXX
.end
With this:
.loadlib XXX
This might be done as part of vsoni's IMCC refactoring, or as a lexer
action that loads the
library as soon as this
在 2006/7/12 上午 12:22 時，Chip Salzenberg 寫到：
In short, to say that :immediate is unpredictable is to make a null
statement, because in practice, all computation is unpredictable.
Yes. And it is the designer's choice to introduce unpredictability into
the PIR level. If the designer allows
在 2006/7/12 上午 12:40 時，chromatic via RT 寫到：
To follow this argument logically, I don't see alternatives besides
removing :init or sandboxing all potentially destructive operations
-- and I
have plenty of Perl 5 code that legitimately deletes files in BEGIN
blocks as
evidence that this
在 2006/7/12 上午 12:33 時，chromatic via RT 寫到：
Because people might write code, by hand, that does careless things
in :immediate subs?
Yes. This is the difference between forcing syntax highlighters,
security checkers,
dependency analyzers, and refactoring browsers to run rm-rf, and let
在 2006/7/12 上午 12:51 時，Allison Randal via RT 寫到：
Chip Salzenberg wrote:
[*] Just what it _is_ intended for is an open question. I think
the user
base will answer it, if we let them, in time.
To give a concrete and immediately relevant example: the fact that
people are using
在 2006/7/12 上午 12:57 時，chromatic 寫到：
On Tuesday 11 July 2006 21:45, Audrey Tang wrote:
If you think PIR is a language for people to write manually to
code applications in, _and_ it has some legitimate use for
deleting files
in :immediate blocks, then your argument may make some sense
在 2006/7/12 上午 1:12 時，Allison Randal via RT 寫到：
Audrey Tang wrote:
That is a sane argument, which is why I think punt-and-see has
some merit:
as soon as there is a workaround forced to be expressed at :immediate
level, we can evaluate it and see if it's better handled
declaratively
在 2006/7/5 上午 12:15 時，chromatic 寫到：
On Tuesday 04 July 2006 21:01, Audrey Tang wrote:
Hence I'm puzzled why you raise the dynamic language categorization
as a justification, for that term usually refers to dynamic typing,
not to :immediate. If it is referring to :immediate, then Python
annotating the type of the variable. Audrey Tang explained that a
similar construct is available. This was followed by a
discussion on the
subject of class prototypes as default values for typed
variables, as
well as philosophical issues.
http://xrl.us/oxxd
Instance
在 2006/7/6 上午 3:30 時，Allison Randal 寫到：
Quick question, is there a syntax specified in Perl 6 for referring
to namespaces from other languages?
I'm reviewing the namespaces PDD and want to update this snippet:
--
IMPLEMENTATION EXAMPLES: Suppose a Perl program were to import some
Tcl
在 2006/7/5 上午 3:06 時，Allison Randal 寫到：
Audrey Tang wrote:
But I guess this bug ticket is not an appropriate place...
Indeed. We need a Document :immediate ticket.
I already filed that as #39716 a few hours ago; also #39715 and
#39714, as per your suggestion:
[TODO] Document IMCC's
(Cross-posted from http://pugs.blogs.com/pugs/2006/07/
v6pm_now_runs_t.html)
Due to clkao++ and fglock++'s work, the CPAN version of v6.pm now
passes all Pugs sanity tests, up and including the Perl 6 Test.pm:
# http://search.cpan.org/dist/v6-pugs/
#
在 2006/7/5 上午 1:26 時，George Wood 寫到：
Here are some probably for Audrey...
1. Page on Perl 6 on Haskell - Is runtime Specific AST actually
the file Language.TH.Sytnax?
Well, no, it's probably best to call it Pugs.AST, and link to src/
Pugs/AST.hs.
2. I am still trying to distinguish
Hi Flavio:
You asked me on #perl6 to build a Data::Bind binary distribution for
Win32-ActivePerl.
After working on it for 2 hours, I (re)discovered that it's
impossible to do that, using the current generation of gratis
downloads of Visual Studio C++ Express 2005, as it seems that Perl
(Mail.app totally scrambled the previous mail; sorry about this re-
post.)
I'm glad to announce that Pugs 6.2.12 is now available from CPAN:
http://search.cpan.org/dist/Perl6-Pugs-6.2.12/
SIZE: 2693459
SHA1: c9731da8e597591ca7e279766481ce0bece8cfa4
This release features much
在 2006/7/4 下午 8:50 時，Allison Randal via RT 寫到：
The :immediate feature isn't really a question of reentrancy (it
doesn't
hold static data over successive calls, and it doesn't return a
pointer
to static data).
That depends on the :immediate code. The equivalence of
BEGIN {
1 - 100 of 167 matches
Mail list logo
