Re: CPAN - resolving conflicting permissions

Agreed. > Neil Bowers 於 2020年9月18日 上午5:10 寫道： > > Hi Audrey, > > I’m one of the PAUSE admins. I’m working through situations where > distributions have split ownership, and/or have permissions conflict with > other distributions. Your i18n distribution is one of these, caused by > earlier

Re: PAUSE permissions clash between I18N::String and i18n::string

Certainly. This is done as i18n-0.11. Thanks for your work! Cheers, Audrey > Neil Bowers 於 2016年8月10日 上午6:10 寫道： > > Hi all, > > I’m one of the PAUSE admins. I’m emailing you because I’m working on > resolving conflicts caused by PAUSE now considering package names

Re: Infrastructure & Communication

> On Apr 29, 2016, at 5:25 PM, Alexander Berntsen wrote: > especially not SaaSS which theoretically can just get rid of all your data > without you having a say. There is a fix for that — Sandstorm.io (self-hosted, not SaaSS) with

[rt.cpan.org #111897] Re: PAR Question Solaris 10

Tue Feb 09 08:45:40 2016: Request 111897 was acted upon. Transaction: Ticket created by audr...@audreyt.org Queue: PAR Subject: Re: PAR Question Solaris 10 Broken in: (no value) Severity: (no value) Owner: Nobody Requestors: audr...@audreyt.org Status: new Ticket

[Libreoffice-commits] core.git: Changes to 'refs/changes/46/10746/1'

___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits

[Libreoffice-commits] core.git: Changes to 'refs/changes/46/10746/2'

___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits

[Libreoffice-commits] core.git: Changes to 'refs/changes/45/10745/1'

___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-commits

Re: Incremental compilation

狂风暴雨 1577594...@qq.com 於 2014年9月12日 上午11:41 寫道： Hi Audrey Tang and Steffen Mueller, Thank you a lof for the PAR! I have a problem now, I want compilate with PAR Incrementally , Can't I? You can. First make a .par file: pp -p -Ofoo.par src.pl then feel free to incrementally add more

[Libreoffice-commits] core.git: vcl/source

vcl/source/fontsubset/cff.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 3b38a2342e48a2aec3c2e4f5aebf883db4b84101 Author: Audrey Tang audr...@audreyt.org Date: Tue Aug 5 09:56:53 2014 +0200 fdo#81516 Support fonts like Source Han Sans with 16 FDArray

[Libreoffice-commits] core.git: Branch 'libreoffice-4-3' - vcl/source

vcl/source/fontsubset/cff.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit bff075cbe1b969361a891d43ae24a648aa429373 Author: Audrey Tang audr...@audreyt.org Date: Tue Aug 5 09:56:53 2014 +0200 fdo#81516 Support fonts like Source Han Sans with 16 FDArray

[Libreoffice-commits] core.git: Branch 'libreoffice-4-2' - vcl/source

vcl/source/fontsubset/cff.cxx |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit c1a53308423ebf45c7209ca1359b205b6f0ac236 Author: Audrey Tang audr...@audreyt.org Date: Tue Aug 5 09:56:53 2014 +0200 fdo#81516 Support fonts like Source Han Sans with 16 FDArray

CC0 Universal Decalaration

To the extent possible under law, I waive all copyright and related or neighboring rights to my past future contributions to LibreOffice. http://creativecommons.org/publicdomain/zero/1.0 Cheers, Audrey ___ LibreOffice mailing list

[jira] Updated: (SHINDIG-812) [PATCH] Attach gadgets.window.adjustHeight to the onresize event

[ https://issues.apache.org/jira/browse/SHINDIG-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Audrey Tang updated SHINDIG-812: Attachment: adjustHeight-on-resize-3.diff This is the version as currently used in Socialtext

[jira] Created: (SHINDIG-812) [PATCH] Attach gadgets.window.adjustHeight to the onresize event

: Improvement Components: Features (Javascript) Affects Versions: trunk Reporter: Audrey Tang Priority: Minor Fix For: trunk Attachments: adjustHeight-on-resize.diff The patch below implements the commented TODO functionality of having gadgets

Re: Quick question: (...) vs [...]

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

Re: Quick question: (...) vs [...]

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

Re: syntax question: method close is export ()

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

Re: Edits to submit

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

Re: Edits to submit

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

Re: syntax question: method close is export ()

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

Re: Edits to submit

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

Re: Edits to submit

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

Re: Conceptual questions about Objects

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

Re: Conceptual questions about Objects

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

Re: Conceptual questions about Objects

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

Re: Conceptual questions about Objects

John M. Dlugosz wrote: Seriously, Does this mean that the access of private attributes from trusted classes is a different form? And that's why you need the qualified syntax when I think it should not be necessary in all cases? Or should that passage really say not in non-trusted classes,

Re: Conceptual questions about Objects

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

Re: Conceptual questions about Objects

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

Re: Conceptual questions about Objects

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

Re: our methods?

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

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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.[]

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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).

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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

Re: our methods?

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

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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.[]

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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).

Re: S09 editorial fixes

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

Re: S09 editorial fixes

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

patch applied (ghc): * ghc-asm: Finally did away with $* in a way that works with Perl 5.6~5.10+, by appending /m to all regexes.

Mon Jul 30 05:22:16 PDT 2007 [EMAIL PROTECTED] * * ghc-asm: Finally did away with $* in a way that works with Perl 5.6~5.10+, by appending /m to all regexes. M ./driver/mangler/ghc-asm.lprl -394 +382 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org

patch applied (ghc): Revert the $* patch for earlier Perls as it breaks the build. Sorry. :/

Wed Jul 11 22:43:51 PDT 2007 [EMAIL PROTECTED] * Revert the $* patch for earlier Perls as it breaks the build. Sorry. :/ M ./driver/mangler/ghc-asm.lprl -1 +4 ___ Cvs-ghc mailing list Cvs-ghc@haskell.org

Re: Generalizing ?? !!

在 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

Re: Generalizing ?? !!

在 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

Re: .perl, nested arrays, parens and a bug with .perl after hyperop

在 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

Re: .perl, nested arrays, parens and a bug with .perl after hyperop

在 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

Re: pugs: aborting smoke tests

在 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:

Re: [perl #41617] make test-pir fails on x86 linux, r14402

在 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

Re: [perl #41617] make test-pir fails on x86 linux, r14402

在 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

Re: Packed array status?

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

Re: Packed array status?

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

Re: Packed array status?

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

Re: Packed array status?

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

Re: recent changes

在 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

Re: recent changes

在 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

Re: Pugs on Windows

在 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

[jifty-devel] length is 42 deprecated in Jifty::DBI::Schema

In order to agree with Jifty::Action's param, as well as to not clobber user code's use of CORE::length(), the new release (0.32) of Jifty::DBI now introduces two deprecation warnings: *** Due to an incompatible API change, the length field in Jifty::DBI columns has been renamed to

[jifty-devel] Re: Template::Declare API deprecation

在 Jan 18, 2007 12:50 PM 時，Jesse Vincent 寫到： Is anyone using get_current_attr in Template::Declare or the Jifty-Template branch of Jifty? Not in user code here, no. Audrey ___ jifty-devel mailing list jifty-devel@lists.jifty.org

Re: hello, does anybody who knows the svn respo of synopsis docs?

在 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

[jifty-devel] Re: [Jifty-commit] r2305 - Template-Declare/lib/Template/Declare

在 Dec 7, 2006 12:37 AM 時，Jesse Vincent 寫到： On Thu, Dec 07, 2006 at 12:27:59AM +0800, Audrey Tang wrote: Next question: If I can make this work, would you be happy to see it happen? div { attr { id = 'foo' } p { 'some text -- semicolon is optional after the closing

Re: [Haskell] ANNOUNCE: QuickCheck 2 development version

在 Nov 24, 2006 9:29 PM 時，Björn Bringert 寫到： This is just a quick announcement that the development version of QuickCheck 2 is now available in a public darcs repository. Some highlights: - Shrinks failing test cases. - Supports testing monadic code. Wonderful. Many thanks for QC2! :-) By

ANN: Pugs Repository URL Changed.

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,

Re: mmd-draft.txt

在 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

Re: mmd-draft.txt

在 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

Re: variables inside an eval

在 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

Re: variables inside an eval

在 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

Re: [Haskell] Pugs gains SMP parallelism support.

在 Oct 21, 2006 5:14 PM 時，Taral 寫到： On 10/21/06, Audrey Tang [EMAIL PROTECTED] wrote: let proc n x = do Hmm, am I missing something here, but how does forkIO (and data parallelism) fit in into that scheme? I R DUM. let proc n x = forkIO $ do I just implemented it that way

[Haskell] Pugs gains SMP parallelism support.

I hacked +RTS -N support into Pugs today; here's a short writeup: http://pugs.blogs.com/pugs/2006/10/smp_paralleliza.html Pugs's current implementation for concurrent operations on lists is very naive: chan- newChan forM ([0..] `zip` xs) $ \(n, x) - forkIO $

[Haskell] ANN: Pugs 6.2.13

(Cross-posted to haskell@, at the suggestion from Don Stewart) 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:

[ANNOUNCE] Pugs 6.2.13 released!

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,

[ANNOUNCE] Pugs 6.2.13 released!

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,

[ANNOUNCE] Pugs 6.2.13 released!

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,

Re: Runtime Role Issues

在 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

Re: Runtime Role Issues

在 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

Re: Nested statement modifiers.

在 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/

Re: Nested statement modifiers.

在 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,

Re: error when using - as lambda function

在 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

Re: error when using - as lambda function

在 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

Re: Nested statement modifiers.

在 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/

Re: Nested statement modifiers.

在 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,

Re: trying to use a role within a role

在 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;

Re: trying to use a role within a role

在 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

Re: trying to use a role within a role

在 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;

Re: trying to use a role within a role

在 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

Re: Motivation for /alpha+/ set Array not Match?

在 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

Re: Motivation for /alpha+/ set Array not Match?

在 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

patch applied (ghc): In ByteCodeGen, correctly passthru AnnCast in all relevant places, so the previous band-aid fix is no longer needed.

Fri Sep 22 22:28:15 PDT 2006 [EMAIL PROTECTED] * In ByteCodeGen, correctly passthru AnnCast in all relevant places, so the previous band-aid fix is no longer needed. M ./compiler/ghci/ByteCodeGen.lhs -7 +7 ___ Cvs-ghc mailing list [EMAIL

patch applied (ghc): * TypeRep.lhs and TypeRep.lhs-boot didnapos; t agree on their signatures (SuperKind vs Kind)

Wed Sep 20 18:25:31 PDT 2006 [EMAIL PROTECTED] * * TypeRep.lhs and TypeRep.lhs-boot didn't agree on their signatures (SuperKind vs Kind) M ./compiler/types/TypeRep.lhs +1 M ./compiler/types/TypeRep.lhs-boot -3 +5 ___ Cvs-ghc mailing list

patch applied (ghc): In tcSplittyConApp_maybe, add the PredTy case

Sat Sep 23 23:32:08 PDT 2006 [EMAIL PROTECTED] * In tcSplittyConApp_maybe, add the PredTy case such that this can compile again: newtype Moose = MkMoose () deriving (Eq, Ord) M ./compiler/typecheck/TcType.lhs +2 ___ Cvs-ghc mailing

patch applied (ghc): Add explicit eta-reduction to GHCIapos; s schemeE such that deriving Typeable wonapos; t panick.

Fri Sep 22 22:09:29 PDT 2006 [EMAIL PROTECTED] * Add explicit eta-reduction to GHCI's schemeE such that deriving Typeable won't panick. M ./compiler/ghci/ByteCodeGen.lhs +7 ___ Cvs-ghc mailing list [EMAIL PROTECTED]

patch applied (ghc): Repair quot; ghciquot; under FC+AT by handling AnnCast in bytecode generator.

Thu Sep 21 21:06:18 PDT 2006 [EMAIL PROTECTED] * Repair ghci under FC+AT by handling AnnCast in bytecode generator. M ./compiler/ghci/ByteCodeGen.lhs +3 M ./compiler/iface/IfaceSyn.lhs -1 +1 M ./compiler/typecheck/TcRnDriver.lhs +1 ___

patch applied (ghc): Another s/autrijus/audreyt/ in comments.

Tue Sep 12 05:13:23 PDT 2006 [EMAIL PROTECTED] * Another s/autrijus/audreyt/ in comments. M ./compiler/parser/Parser.y.pp -1 +1 ___ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc

patch applied (ghc): Comment-only: Fix a typo, and note that the PredTy case on SplitTyConApp_maybe was added as a kluge.

Sun Sep 24 05:31:51 PDT 2006 [EMAIL PROTECTED] * Comment-only: Fix a typo, and note that the PredTy case on SplitTyConApp_maybe was added as a kluge. M ./compiler/typecheck/TcType.lhs -2 +8 ___ Cvs-ghc mailing list [EMAIL PROTECTED]

  1   2   3   4   >