I can see why we wouldn't want to include YAML, and won't cry for *too
long* if it doesn't go in ;), but here are some reasons why I'd like for
full YAML to be a part of the spec:
- marshaling data structures between the application being tested and
the test harness (strings are nice, but full Per
Whoa whoa whoa slow down there folks...
Some people seemed to have misrecognised those keys as YAML.
It was NEVER meant to be YAML.
The idea was to use something more like MIME headers.
We all agreed that we DIDN'T want the format to be too heavy, and going
with MIME or MIME-alike seemed the
- Original Message
From: Adam Kennedy
> Whoa whoa whoa slow down there folks...
>
> Some people seemed to have misrecognised those keys as YAML.
>
> It was NEVER meant to be YAML.
>
> The idea was to use something more like MIME headers.
Well, regardless of what those lines a
On Tue, Jul 11, 2006 at 12:24:47AM -0500, Vishal Soni wrote:
> Other thing I could do is re-allocate the Macro Array size when it gets
> full. So it would not fail until system starts swapping :-)
>
> I would prefer the second option. Because it might hinder your and other
> language development.
On Mon, Jul 10, 2006 at 03:55:25PM -0700, Darren Duncan wrote:
> I believe that the current Test.pm already qualifies as a baby-Perl
> implementation, as overall its functionality is quite simple, and it
> uses very little of the language (especially since its use of
> junctions was removed a fe
Just some random thoughts about self-referential structures
and their literal representations:
$ perl -MData::Dumper -e '$a=[1,\$a]; print Dumper($a)'
$VAR1 = [
1,
\$VAR1
];
$ perl -MYAML -e '$a=[1,\$a]; print Dump($a)'
--- &1
- 1
- !perl/ref:
=: *1
$ pugs -e 'my @a =
On a form the submit button looks like this:
when this form is submitted using
$w->submit_form (
fields => {
fname => 'Foo',
});
the field submit and its value Update does not seem to be sent
to web server. If I add
submit => 'Update',
to the list of the
PRuby is the project.
Suggestions of a better project name are welcome.
Ronie, or better Ronin if decent backronym can be found.
Brad
--
Furthermore, when experiencing a rush of blood to the head, if one
puts spittle on the upper part of one's ear, it will soon go away.
Punie has an example of optok parsing.
APL has an example of utf-8 grammar.
Regards.
On Jul 11, 2006, at 12:37 AM, Vishal Soni wrote:
Thanks Chris
I looked at it but it does not implement Unicode in PGE and Optok
too..
On Mon, 2006-07-10 at 23:30 -0500, Chris Dolan wrote:
On Jul 10, 20
# New Ticket Created by Michal Jurosz
# Please include the string: [perl #39788]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39788 >
Hello,
attached patch probably fixes examples/shootout errors (
http://shootout.alio
S02 and S06 discuss containers quite a bit. They say things like:
"The is NAME (DATA) syntax defines traits on containers and
subroutines" -S06
"A variable object may itself be bound to a container type that
specifies how the container works without necessa
On Sat, Jul 08, 2006 at 07:01:19PM -0500, Steven Pritchard wrote:
> First, there is a hardcoded "lib" somewhere that I can't seem to find.
OK, I finally found the (last, I hope) problem. In
tools/dev/install_files.pl, there is this line:
$dest =~ s/^runtime/lib/;
I may have gone overboa
On Tue, Jul 11, 2006 at 01:47:26PM +0300, Gabor Szabo wrote:
> On a form the submit button looks like this:
>
>
>
> when this form is submitted using
>
> $w->submit_form (
>fields => {
>fname => 'Foo',
>});
>
> the field submit and its value Update does not seem to
the field submit and its value Update does not seem to be sent
to web server. If I add
submit => 'Update',
That's right. It's possible to submit a form without specifying a
submit button. If you want the submit button clicked, then you have
to explicitly specify it.
Also, th
On 7/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> How can I fix this?
WWW::Mechanize(3pm)
$mech->submit_form( ... )
This method lets you select a form from the previously fetched page,
fill in its fields, and submit it. It combines the form_number/form_name,
set_
On Jul 11, 2006, at 9:07 AM, Gabor Szabo wrote:
If button is not passed, then the "submit()" method is used
instead.
Perhaps it could be clearer then: submit() does not pass any button
unless you specify it.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On 7/11/06, Andy Lester <[EMAIL PROTECTED]> wrote:
On Jul 11, 2006, at 9:07 AM, Gabor Szabo wrote:
> If button is not passed, then the "submit()" method is used
> instead.
Perhaps it could be clearer then: submit() does not pass any button
unless you specify it.
Yes maybe that, in addit
On 7/11/06, Gaal Yahas <[EMAIL PROTECTED]> wrote:
On Mon, Jul 10, 2006 at 03:55:25PM -0700, Darren Duncan wrote:
> I believe that the current Test.pm already qualifies as a baby-Perl
> implementation, as overall its functionality is quite simple, and it
> uses very little of the language (especia
I mentioned YAML with a pretense I failed to mention -- that we
wouldn't parse the YAML. That's already been done, and there are
plenty of parsers.
YAML has clear designations of where it starts and ends. A TAP parser
wouldn't have to look at the diagnostics and guess what it is.
If the data str
On Jul 11, 2006, at 7:34 AM, Ian Langworth wrote:
Maybe we don't care. Maybe we can simply add a callback for some
diagnostic_block_analyzer() and, in my own little happy world,
$parser->diagnostic_block_analyzer( sub {
my ($block) = @_;
if ($block =~ m{ \A --- }xs) {
do something
On 7/11/06, Jonathan T. Rockway <[EMAIL PROTECTED]> wrote:
Ian Langworth wrote:
> I mentioned YAML with a pretense I failed to mention -- that we
> wouldn't parse the YAML. That's already been done, and there are
> plenty of parsers.
I agree with this. YAML has been done and done again, in ev
- Original Message
From: Jonathan T. Rockway <[EMAIL PROTECTED]>
> However, if you wanted to make *me* happy ;), why not make the whole
> darn thing a YAML stream like this:
> ---
> test: Test whether foo + bar = baz
> result: ok
> sequence: 1
> ---
Aside from the fact that many langua
- Original Message
From: Jonathan Rockway <[EMAIL PROTECTED]>
> What else is TAP targeted to? C / C++ / Java?
Java programmers typically use jUnit. C programmers have libtap available.
PHP tests often use TAP (don't know the name) and Javascript has Test.Simple,
though it parses the
if i recall correctly, syck doesn't handle utf-8/16. does/will tap
care about that?
That's true -- I think Audrey patched the perl version to work properly,
but I forgot that other languages are without that functionality. Ruby
doesn't properly support Unicode either, so Unicode support pro
Ovid wrote:
> - Original Message From: Jonathan Rockway <[EMAIL PROTECTED]>
>
>> What else is TAP targeted to? C / C++ / Java?
>
>
> PHP tests often use TAP (don't know the name)
almost all of the php test frameworks now offer TAP support - see
http://search.cpan.org/dist/Test-Harn
Ian Langworth wrote:
I mentioned YAML with a pretense I failed to mention -- that we
wouldn't parse the YAML. That's already been done, and there are
plenty of parsers.
I agree with this. YAML has been done and done again, in every
language. It works, it's tested. I don't think we need E
I was having that problem too going over S09. It seems like we need to get
the glossary together like Uri was saying that we can have a controlled
language for creating the documents. If we dont have one already, I suggest
we start one.
Jordan
On 7/11/06, Aaron Sherman <[EMAIL PROTECTED]> wrot
On Tue, 2006-07-11 at 10:06 -0400, Aaron Sherman wrote:
> For example:
>
> our List multi Container::each(Container [EMAIL PROTECTED])
In thinking about each, I've come across an interesting need. I wrote
this example:
for each(=<>; 1..*) -> ($line, $lineno) {
say "$lineno: $line";
}
Whic
On Tue, 2006-07-11 at 09:28 -0500, Jordan Kanter wrote:
> I was having that problem too going over S09. It seems like we need to get
> the glossary together like Uri was saying that we can have a controlled
> language for creating the documents. If we dont have one already, I suggest
> we start o
In a message dated Tue, 11 Jul 2006, Aaron Sherman writes:
But would it be reasonable to also provide a named-only parameter to
each for that purpose?
our List multi Container::each(Bool :$stop, Container [EMAIL PROTECTED])
So that:
for each(:stop, =<>; 1..*) -> ($line, $lineno) {
say "$line
> However, most perl tests don't care about TAP, they use Test::More and
> Test::Harness and happen to exchange data via TAP. If Test::More and
> Test::Harness decied to use "YAP" (YAML Anything Protocol? :), then most
> applications would probably never notice.
most _perl_ applications would ne
On Tue, Jul 11, 2006 at 05:07:02PM +0300, Gabor Szabo wrote:
> From the documentation it is not clear (to me) why is the value of the
> submit
> button sent only if I specify button => button
> The doc only sais this:
>
> If button is not passed, then the "submit()" method is used instead.
Aside from the fact that many languages are already using the TAP protocol and
we'd create something they *don't* use, what happens when my 4,000 test lines
all of a sudden become 16,000 test lines because the format has been changed?
Do you pay for CPU time on a per-newline basis? :)
Goo
On Jul 11, 2006, at 09:21, Ovid wrote:
Java programmers typically use jUnit. C programmers have libtap
available. PHP tests often use TAP (don't know the name) and
Javascript has Test.Simple, though it parses the test results
directly and then outputs TAP (if I recall correctly).
It bot
# New Ticket Created by Jerry Gay
# Please include the string: [perl #39791]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39791 >
everybody wanted the colon, and now we have it. it's time to lop off
@these ungainly [EMAIL
On Tue, 2006-07-11 at 09:53 -0700, Trey Harris wrote:
> In a message dated Tue, 11 Jul 2006, Aaron Sherman writes:
> > But would it be reasonable to also provide a named-only parameter to
> > each for that purpose?
> It sounds reasonable to me, but :stop reads badly. Maybe C<:strictly>?
> Maybe
In a message dated Tue, 11 Jul 2006, Aaron Sherman writes:
On Tue, 2006-07-11 at 09:53 -0700, Trey Harris wrote:
It sounds reasonable to me, but :stop reads badly. Maybe C<:strictly>?
Maybe it's not a function of a flag to each, but a marking that certain
lists should be tapped non-exhaustively
On Tue, 2006-07-11 at 12:50 -0700, Trey Harris wrote:
> > But I don't think that will do, because it fails when you don't know
> > WHICH list would be the longest (or you have to specify them all
> > as :with, and that's rather counter-intuitive). Perhaps a stand-alone
> > adverb, :parity makes mo
On Tue, 2006-07-11 at 16:22 -0400, Aaron Sherman wrote:
> zip(:fewest, @a;@b;@c); # Until one runs out
Once again, I missed some Larry magic. He already selected ":shortest"
for this, so I guess on roundrobin, it's ":longest"... ignore my
choices.
I think just like Larry, but 1,000 times slower
There's a bit at the end of the current S29:
=item A/S??: OS Interaction
I've taken on a few of these, and in doing so found that I was making
some assumptions. I'd like to share those and see if they make sense:
* POSIX will be a low-level module that slavishly reproduces the
POS
On Tue, Jul 11, 2006 at 16:46:40 -0400, Aaron Sherman wrote:
> There's a bit at the end of the current S29:
>
> =item A/S??: OS Interaction
>
> I've taken on a few of these, and in doing so found that I was making
> some assumptions. I'd like to share those and see if they make sense:
>
>
I've finished rewriting the ruby cvs yacc grammar to PGE.
I had to fix quite a few left recursion problems to eliminate infinite
recursion.
It parses my simple puts.rb example, but parse time is really slow.. 2
minutes.
I'm sure I've made some dumb grammar mistakes that is slowing it down.
The Perl 6 Internals correction summary for the weeks of 2006-02-13 through
2006-02-28
Summary updates
Thank you to everyone who took the time to point out that I had
accidently used February 2003 rather than 2006 for the internals
section. This is the actual summary for February 20
# New Ticket Created by Autrijus Tang
# Please include the string: [perl #39792]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39792 >
Currently :immediate in PIR serves two purposes: Running loadlib for
type lookups, an
Re more powerful constant creation:
There's already a VTABLE method for constructing PMCs from STRINGs, e.g:
=item C
Class method to construct an array from the string representation C,
which is a string I<"(el0, el1, ...)">.
used for creating param/args signature arrays inside
src/pmc/fixedint
Aargh! It gets annoying that the reply goes directly to the author rather than
the list.
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
- Forwarded Me
Leaving :immediatein PIR doesn't actually introduce any problems that we
didn't already have (and can't escape anyway).
There's a PIR file already in svn somewhere in Parrot where a :immediate
function is used to build a large table programmatically at compile time, so
that at runtime it's already
I needed some code to trawl through a directory tree parsing perl
modules and scripts to determine their dependencies.
The closest existing CPAN code was Module::Dependency but it fell short
of what I needed. The original author (P Kent) has passed over
maintenance to me. My latest release is:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Moin Tim,
On Tuesday 11 July 2006 18:34, Tim Bunce wrote:
> I needed some code to trawl through a directory tree parsing perl
> modules and scripts to determine their dependencies.
>
> The closest existing CPAN code was Module::Dependency but it fell
Tels wrote:
My idea was to build _only_ the database, and do it right, simple and easy
to use and then get everyone else to just use the DB instead of fiddling
with their own. (simple by having the database being superior to every
other hack thats in existance now :-)
I even got so far as to
在 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 o
On Tue, Jul 11, 2006 at 04:31:36PM -0700, Chip Salzenberg wrote:
>
> There's a PIR file already in svn somewhere in Parrot where a :immediate
> function is used to build a large table programmatically at compile time, so
> that at runtime it's already completely available. That's neat.
Yep. It'l
Thanks, applied as r13258.
From: Audrey Tang <[EMAIL PROTECTED]>
Date: Tue, 4 Jul 2006 23:54:30 -0400
. . .
Well, I'm curious, as the only dynamic language with this feature --
Perl5 namely -- does not target Parrot, and the current users of this
feature is out of necessity for working around the dynl
在 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
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 dire
Geoffrey Young wrote:
However, most perl tests don't care about TAP, they use Test::More and
Test::Harness and happen to exchange data via TAP. If Test::More and
Test::Harness decied to use "YAP" (YAML Anything Protocol? :), then most
applications would probably never notice.
most _perl_ appli
On Tue, Jul 11, 2006 at 09:59:12PM -0400, Audrey Tang wrote:
> ?b 2006/7/11 ?U?? 7:33 ???AChip Salzenberg via RT ?g???G
> >Now think about the alternatives if your goal is to have the table ready
> >to go at runtime without any computational overhead at all.
>
> And if we can restrict :immediate u
On Tue, Jul 11, 2006 at 11:52:10PM -0400, Bob Rogers wrote:
>Even so, I can't see how it would help to use :immediate to compile
> Common Lisp.
That's fine; some misconceptions to the contrary, that's not what it's
intended for.[*] It's an *analogue* of Perl's BEGIN; it's not intended to
be a
在 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 rand(
On Tuesday 11 July 2006 21:09, Audrey Tang wrote:
> I really cannot argue with that argument (essentially "let's punt and
> see"); therefore this ticket is probably best reserved until Parrot actually
> has a security model, in which time I'll then argue that :immediate should
> be subjected t
On Tuesday 11 July 2006 21:29, Audrey Tang wrote:
> Yes. And it is the designer's choice to introduce unpredictability into
> the PIR level. If the designer allows rand() inside :immediate, it's
> the designer's call; if the designer allows rm -rf, it's again the
> designer's call.
I'm sorry, b
在 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 potent
在 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
use
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 :immediate to load libraries at compile-time is a good
sign t
在 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 :immedia
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.
Come on, Audrey! That's a strawman argum
在 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.
Co
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.
Excellent. (Er, though you know that .loadlib isn't reall
在 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.
Ex
On Jul 12, 2006, at 12:49 AM, Kevin Tew wrote:
Has anyone done anything about coverity, whats the next course of
action?
I'd be happy to send off an email and start a conversation with
coverity if that is what is needed.
My gut feel is that we're too early to start throwing things at
Cov
Has anyone done anything about coverity, whats the next course of action?
I'd be happy to send off an email and start a conversation with coverity
if that is what is needed.
Has anyone done anything with splint yet?
Kevin
On Tuesday 11 July 2006 22:49, Kevin Tew wrote:
> Has anyone done anything about coverity, whats the next course of action?
> I'd be happy to send off an email and start a conversation with coverity
> if that is what is needed.
I talked to them after their first big announcement. They'll look in
74 matches
Mail list logo
