When I first installed parrot, curses worked with it, but it fails to work
anymore for me, either under darwin or freebsd. On darwin, it clears the
screen, and can only read "assertation failed" before it clears and dies,
so I can't see diagnostics, but under freebsd I get this.
Couldn't load 'li
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> Quick question for Tcl folks. Currently, store_lex is *always* an
> aliasing operation. That is, after
>
>store_lex 'a', $P0
>
> the old PMC that used to be accessible by
>
>$P1 = find_lex 'a'
>
> is now gone (unless you kept a reference somewh
A. Pagaltzis wrote:
* Adam Kennedy <[EMAIL PROTECTED]> [2005-11-23 01:40]:
And XML was designed for, and still remains VERY good at, doing
neutral format data interchange.
Another option if you want a lightweight format for structured
data is JSON. XML is very nice for documents, particularl
On Nov 22, 2005, at 11:06 AM, Leopold Toetsch wrote:
dynclasses/dynlexpad.pmc provides (or should eventually provide) a
more dynamic lexpad (similar to the deprecated scratchpad.pmc).
It's not finished yet, it doesn't consult LexInfo for static
lexicals yet.
Before working more on it, I'
Quick question for Tcl folks. Currently, store_lex is *always* an
aliasing operation. That is, after
store_lex 'a', $P0
the old PMC that used to be accessible by
$P1 = find_lex 'a'
is now gone (unless you kept a reference somewhere else).
(To modify an existing lexical, the sequence is
On 11/22/05, Larry Wall <[EMAIL PROTECTED]> wrote:
> What tipped me over the edge, however, is that I want ^$x back for a
> unary operator that is short for 0..^$x, that is, the range from 0
> to $x - 1. I kept wanting such an operator in revising S09. It also
> makes it easy to write
>
> for
On Wed, 2005-11-23 at 01:39 +0100, Leopold Toetsch wrote:
> But my argument was: whenever you
> start introspecting a call frame, by almost whatever means, this will
> keep the call frame alive[1] (see Continuation or Closure). That is:
> timely destruction doesn't work for example...
Destruct
* Adam Kennedy <[EMAIL PROTECTED]> [2005-11-23 01:40]:
> And XML was designed for, and still remains VERY good at, doing
> neutral format data interchange.
Another option if you want a lightweight format for structured
data is JSON. XML is very nice for documents, particularly with
mixed content;
On Nov 22, 2005, at 1:40, Matt Fowles wrote:
Call Frame Access
Chip began to pontificate about how one should access call frames.
Chip
suggested using a PMC, but Leo thought that would be too slow.
No, not really. It'll be slower, yes. But my argument was: whenever you
start int
Do you still think that YAML is a good intermediate format choice? Do you think
an integration with other standard utilities to produce YAML would be possible
(prove, etc)?
YAML has a few ... issues. :/
I've laid them out before at http://cpanratings.perl.org/dist/YAML
Brian has said that the
I'm changing my mind about type sigils. After playing around with ^
for a while, I find it's useful only in signatures and declarations,
and I'm generally forced to omit it when using it within inner
declarations, or it would redeclare the type. Taking that together
with the fact that it installs
On Nov 22, 2005, at 19:52, Chip Salzenberg wrote:
On Tue, Nov 22, 2005 at 05:50:39PM +, Roger Browne wrote:
Why not use "," instead of "->"?
Indeed. We shouldn't introduce "->" at this point, when we already
use the perfectly serviceable comma for analogous cases.
Done, r10140.
leo
I wrote:
> > I'd prefer to ask for mappings explicitly, e.g. something like this:
> >
> >.HLL "Tcl", "tcl_group"
> >...
> >$P0 = new Integer # really Integer
> >$P1 = new_mapped Integer # really TclInteger
Chip wrote:
> Hm. Why?
Because you don't always want a mapped ty
Michael,
On Nov 22, 2005, at 3:13 PM, Michael Peters wrote:
Stevan Little wrote:
Michael,
You might want to look at some of the work on the Pugs test suite.
http://m19s28.vlinux.de/cgi-bin/pugs-smokeserv.pl
It uses (among other things) Test::TAP::Model and
Test::TAP::HTMLMatrix, and uses YAM
On Tue, Oct 18, 2005 at 07:38:19PM -0400, Stevan Little wrote:
> I have been meaning to do some kind of p5 prototype of this, I can
> push it up the TODO list if it would help you.
As you can probably infer from the amount of time that it has taken for me
to realise that I've failed to reply to
Stevan Little wrote:
> Michael,
>
> You might want to look at some of the work on the Pugs test suite.
>
> http://m19s28.vlinux.de/cgi-bin/pugs-smokeserv.pl
>
> It uses (among other things) Test::TAP::Model and
> Test::TAP::HTMLMatrix, and uses YAML as an intermediate test-run format.
Actual
Adam Kennedy wrote:
> Michael
>
> There's existing work happening in this area you may want to get
> involved in. We even have a draft XML schema that does exactly what you
> are talking about.
>
> Go read http://ali.as/pita/
Definitely an interesting project. It is much wider in scope than my
Michael,
You might want to look at some of the work on the Pugs test suite.
http://m19s28.vlinux.de/cgi-bin/pugs-smokeserv.pl
It uses (among other things) Test::TAP::Model and
Test::TAP::HTMLMatrix, and uses YAML as an intermediate test-run format.
Stevan
On Nov 22, 2005, at 2:11 PM, Mi
Michael
There's existing work happening in this area you may want to get
involved in. We even have a draft XML schema that does exactly what you
are talking about.
Go read http://ali.as/pita/
Then come hang out on irc://irc.perl.org/#pita
Adam K
Michael Peters wrote:
Hello all,
I'm in th
On Tue, Nov 22, 2005 at 09:31:27AM +0200, Gaal Yahas wrote:
: In pugs, r7961:
:
: my @pats = /1/, /2/;
: say "MATCH" if 1 ~~ any @pats; # MATCH
: say "MATCH" if 0 ~~ any @pats; # no match
:
: So far so good. But:
:
: my $junc = any @pats;
: say "MATCH" if 1 ~~ $junc; # n
Hello all,
I'm in the planning stages for a project (brief planning notes
http://examples.petersfamily.org/smolder.html if interested) that will be used
to collect test reports for project and make them viewable on the web.
I want to change as little about the way they run their tests, but still
On Nov 22, 2005, at 18:50, Roger Browne wrote:
Leopold Toetsch wrote:
.HLL_map .LexPad -> .DynLexPad # (2)
Why not use "," instead of "->"? It would be one less special-case for
the PIR programmer to remember.
No problem. If folks prefer a comma I'll change it.
PDD20 says:
On Tue, Nov 22, 2005 at 12:48:39PM -0600, Patrick R. Michaud wrote:
: On Mon, Nov 21, 2005 at 09:02:57AM -0800, Larry Wall wrote:
: > On Sun, Nov 20, 2005 at 10:27:17AM -0600, Patrick R. Michaud wrote:
: > : On Sat, Nov 19, 2005 at 06:32:17PM -0800, Larry Wall wrote:
: > : > We already have, from A
On Nov 22, 2005, at 18:32, Chip Salzenberg wrote:
OTOH, that same case in Perl 6 is a normal closure and is supported
with
the default LexPad:
Ok. I'll change implementation accordingly. Below is the full code of
case 1 / outer.pir
leo
.pragma n_operators 1 # add creates new PMC
On Tue, Nov 22, 2005 at 05:50:39PM +, Roger Browne wrote:
> Leopold Toetsch wrote:
> > .HLL_map .LexPad -> .DynLexPad # (2)
>
> Why not use "," instead of "->"?
Indeed. We shouldn't introduce "->" at this point, when we already
use the perfectly serviceable comma for analogous ca
On Mon, Nov 21, 2005 at 09:02:57AM -0800, Larry Wall wrote:
> On Sun, Nov 20, 2005 at 10:27:17AM -0600, Patrick R. Michaud wrote:
> : On Sat, Nov 19, 2005 at 06:32:17PM -0800, Larry Wall wrote:
> : > We already have, from A5, \x[0a;0d], so you can supposedly say
> : > "\x[123a;123b;123c]"
> :
On Tue, Nov 22, 2005 at 10:30:20AM -0800, Larry Wall wrote:
> On Tue, Nov 22, 2005 at 09:46:59AM -0800, Dave Whipp wrote:
> : Larry Wall wrote:
> :
> : >And there aren't that many regexish languages anyway. So I think :syntax
> : >is relatively useless except for documentation, and in practice pe
On Tue, Nov 22, 2005 at 09:46:59AM -0800, Dave Whipp wrote:
: Larry Wall wrote:
:
: >And there aren't that many regexish languages anyway. So I think :syntax
: >is relatively useless except for documentation, and in practice people
: >will almost always omit it, which makes it even less useful, a
On Tue, Nov 22, 2005 at 09:42:38AM -0800, jerry gay wrote:
> your example in the previous message made me think. what will parrot
> do if a parrot sub declares the :outer subpragma, and the sub to which
> it refers doesn't have a lexical pad?
Nothing; that's entirely legal. And it's even useful,
Leopold Toetsch wrote:
> Before working more on it, I'd like to know from HLL authors, what they
> need.
I don't think I need anything more than :outer and .lex for the Amber
compiler. I certainly don't need to specify or manipulate pad_depth.
> .HLL_map .LexPad -> .DynLexPad # (2)
Larry Wall wrote:
And there aren't that many regexish languages anyway. So I think :syntax
is relatively useless except for documentation, and in practice people
will almost always omit it, which makes it even less useful, and pretty
nearly kicks it over into the category of multiplied entities
your example in the previous message made me think. what will parrot
do if a parrot sub declares the :outer subpragma, and the sub to which
it refers doesn't have a lexical pad? something like:
.sub do_add3
.const .Sub add3 = "add3"
$P1 = newclosure add3
On Tue, Nov 22, 2005 at 09:32:37AM -0800, Chip Salzenberg wrote:
> $P0 = fetch_lex '$a'
I meant "find_lex", of course.
PS: fetch_*, get_*, find_*, ... so many naming conventions, so little
reason for them.
--
Chip Salzenberg <[EMAIL PROTECTED]>
On Tue, Nov 22, 2005 at 03:28:02PM +0100, Leopold Toetsch wrote:
> Below are two cases of inner subs in Perl5 and Python. The first
> (do_add3) is a plain nested subroutine, which is in the call chain. The
> second (mk_add3) uses a closure. perl5 can't deal with case 1 properly
> and warns.
>
>
On Tue, Nov 22, 2005 at 08:19:04PM +1100, Damian Conway wrote:
: >And perhaps we'd want a general form for specifying other
: >pattern syntaxes; i.e., :perl5 and :glob are shortcuts for
: >:syntax('perl5') and :syntax('glob') or something like that.
:
: Agreed.
But the language in the following
Patrick wrote:
Since we already have :perl5, I'd think that we'd want globbing
to be something like
rule jpeg :i :glob /*.jp{e,}g/
or, for something intra-rule-ish:
m :w / mv (:glob *.c)+ /
Here! Here!
And perhaps we'd want a general form for specifying other
pattern syntaxes; i
thanks for the help! I think using the environment variable is a really
easy way to achieve my goal.
thanks again,
michael
On Tue, Nov 22, 2005 at 10:12:00AM +0100, Michele Dondi wrote:
: Oh, I'm not the person you were responding to, and probably the less
: entitled one to speak in the name of everyone else here, but I feel like
: doing so to say that in all earnestness I'm quite sure no one took any
: offense out
On Tue, Nov 22, 2005 at 07:52:24AM -0800, Larry Wall wrote:
>
> I think we'll leave both _ and \_ meaning the same thing, just to avoid
> that confusion path [...]
Yay!
> : Whatever shortcuts we introduce, I'll be happy if we can just
> : rule that backslash+space (i.e., "\ ") is a literal space
dynclasses/dynlexpad.pmc provides (or should eventually provide) a more
dynamic lexpad (similar to the deprecated scratchpad.pmc). It's not
finished yet, it doesn't consult LexInfo for static lexicals yet.
Before working more on it, I'd like to know from HLL authors, what they
need.
Currentl
On Mon, Nov 21, 2005 at 11:25:20AM -0600, Patrick R. Michaud wrote:
: On Mon, Nov 21, 2005 at 09:02:57AM -0800, Larry Wall wrote:
: > : There's also , unless someone redefines the subrule.
: >
: > But you can't use in a character class. Well, that is, unless
: > you write it:
: >
: > <+[ a
Below are two cases of inner subs in Perl5 and Python. The first
(do_add3) is a plain nested subroutine, which is in the call chain. The
second (mk_add3) uses a closure. perl5 can't deal with case 1 properly
and warns.
The question is: should Parrot cover case 1 too with :outer and it's
defau
Selon Dharmesh Vyas <[EMAIL PROTECTED]>:
> Hello Group,
>
> I am trying to test the perl component and find the code coverage for the
> same.I have wrote a parser that analyses the generated perl test log files.
> I am using the version 5.8.7 of perl. I am trying to do the code coverage
> using bu
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2005-11-22 10:10]:
> I haven't found a way to do this with Test::Harness or
> Test::TAP as they currently are.
You could take the id from either the commandline or an
environment variable. Then you could run the harness as something
like
TEST_DB_ID=42
On Tuesday 22 November 2005 01:10, [EMAIL PROTECTED] wrote:
> Hi All,
>
> I have been trying to find a way to combine the functionality of
> Test::Harness with testing scripts that take a parameter.
> Here is my situation: I am trying to test a database configuration for
> one specific ID. This ID
On Mon, 21 Nov 2005, Larry Wall wrote:
I would like to publicly apologize for my remarks, which were far too
harsh for the circumstances. I can only plead that I was trying to
be far too clever, and not thinking about how it would come across.
No, to be perfectly honest, it was more culpable th
On Mon, Nov 21, 2005 at 09:02:57AM -0800, Larry Wall wrote:
> : There's also , unless someone redefines the subrule.
>
> But you can't use in a character class. Well, that is, unless
> you write it:
>
> <+[ a..z ]+>
>
> or some such. Maybe that's good enough.
Er, that's now <+[ a..z ]+s
On Tue, Nov 22, 2005 at 01:09:40AM +0100, Ruud H.G. van Tol wrote:
> 's/$/foo/' becomes 's//foo/'
> >>>
> >>> Uh, no, because is still a zero width assertion. :-)
> >>
> >> That's why I chose it. It is not at the end-of-string?
> >
> > Because ".*" matches "", // would be true at
> > every p
Hi All,
I have been trying to find a way to combine the functionality of
Test::Harness with testing scripts that take a parameter.
Here is my situation: I am trying to test a database configuration for
one specific ID. This ID is essentially part of primary key for several
tables and we would like
On Mon, Nov 21, 2005 at 11:19:48PM +0100, Ruud H.G. van Tol wrote:
> Patrick R. Michaud:
>
> >> 's/$/foo/' becomes 's//foo/'
> >>
> >
> > Uh, no, because is still a zero width assertion. :-)
>
> That's why I chose it. It is not at the end-of-string?
Because ".*" matches "", // would be true
On Mon, Nov 21, 2005 at 07:57:59PM +0100, Ruud H.G. van Tol wrote:
>
> There is a "[[:alpha:][:digit:]" and a "[[:alpha:][:digit]]" on the
> A5-page.
Now fixed.
> > Besides, you have to be able to distinguish
> > s/^/foo/ from s/$/foo/.
>
> 's/$/foo/' becomes 's//foo/'
>
Uh, no, because is s
On Mon, Nov 21, 2005 at 12:08:08PM -0800, Larry Wall wrote:
> On Mon, Nov 21, 2005 at 07:57:59PM +0100, Ruud H.G. van Tol wrote:
> : There is a "[[:alpha:][:digit:]" and a "[[:alpha:][:digit]]" on the
> : A5-page.
>
> Hmm, well, thanks--I went to fix it and I see Patrick beat me to
> the fix. But
Hello Group,
I am trying to test the perl component and find the code coverage for the
same.I have wrote a parser that analyses the generated perl test log files.
I am using the version 5.8.7 of perl. I am trying to do the code coverage
using bullseye. But while I am trying to build the component
HaloO,
Gaal Yahas wrote:
In pugs, r7961:
my @pats = /1/, /2/;
say "MATCH" if 1 ~~ any @pats; # MATCH
say "MATCH" if 0 ~~ any @pats; # no match
So far so good. But:
my $junc = any @pats;
say "MATCH" if 1 ~~ $junc; # no match
say "MATCH" if 0 ~~ $junc; # no match
54 matches
Mail list logo
