With patches from myself (to tcl) and leo (to parrot), partcl is once
again passing 100% of the tests, using PDD20.
The biggest hurdle was having some arbitrary (non :lex-ified) parrot
sub issue our find_lex and store_lex for us to ease transition. As
more of tcl becomes compiled, we can pr
On Mon, Nov 28, 2005 at 01:16:49PM -0500, Will Coleda wrote:
> With patches from myself (to tcl) and leo (to parrot), partcl is once
> again passing 100% of the tests, using PDD20.
Yay!
> The biggest hurdle was having some arbitrary (non :lex-ified) parrot
> sub issue our find_lex and store_l
On Nov 28, 2005, at 2:46 PM, Chip Salzenberg wrote:
On Mon, Nov 28, 2005 at 01:16:49PM -0500, Will Coleda wrote:
With patches from myself (to tcl) and leo (to parrot), partcl is once
again passing 100% of the tests, using PDD20.
Yay!
The biggest hurdle was having some arbitrary (non :lex-i
It used to be that WWW::Mechanize was a "good enough" testing tool for
my web applications.
It doesn't do Javascript, but I used very minimal
Javascript and thus worked around that limitation.
Along comes AJAX. It offers benefits that make JavaScript seem worth
using.
But now how I can test t
On Mon, Nov 28, 2005 at 08:25:48PM +, Mark Stosberg wrote:
> It used to be that WWW::Mechanize was a "good enough" testing tool for
> my web applications.
>
> It doesn't do Javascript, but I used very minimal
> Javascript and thus worked around that limitation.
>
> Along comes AJAX. It offer
--- Mark Stosberg <[EMAIL PROTECTED]> wrote:
> What are other folks doing to test web applications that make heavy
> use
> of JavaScript?
If you want to leverage your Perl testing knowledge, you can check out
Test.Simple from JSAN:
http://openjsan.org/doc/t/th/theory/Test/Simple/0.21/index.html
On Mon, Nov 28, 2005 at 20:25:48 +, Mark Stosberg wrote:
> But now how I can test the application? I have a link that uses AJAX to
> pull in some content that gets displayed in a new layer, including a
> form I'd like to submit.
http://www.qapodcast.com/news/2005/11/02/qa-podcast-7-talking-sel
On Mon, Nov 28, 2005 at 03:22:10PM -0500, Will Coleda wrote:
> Tcl variables can be either globals or lexicals (inside a [proc]).
> So, all the code to get a PMC from a varname was factored out to a
> single routine that returns the right PMC (global or lexical)
> depending on call level.
I
On Nov 26, 2005, at 22:16, chromatic wrote:
Hi all,
Here's a first shot at Test::More in pure PIR. It only supports
plan(),
ok(), and is() (for integers, floats, strings, and PMCs) right now. If
everyone's reasonably happy, I'll check it in.
chromatic please make that sentence: 'If no on
On 2005-11-28, Ovid <[EMAIL PROTECTED]> wrote:
> --- Mark Stosberg <[EMAIL PROTECTED]> wrote:
>
>> What are other folks doing to test web applications that make heavy
>> use
>> of JavaScript?
>
> If you want to leverage your Perl testing knowledge, you can check out
> Test.Simple from JSAN:
>
> htt
On 2005-11-02, Luke Closs <[EMAIL PROTECTED]> wrote:
>
> Also, yesterday Test::WWW::Selenium was uploaded to CPAN, so Selenium
> can now be driven by perl!
Test::WWW::Selenium seems interesting, but I could use an example it
would be useful to use, versus the standard techniques.
From the docs,
On Mon, Nov 28, 2005 at 10:34:42PM +, Mark Stosberg wrote:
> On 2005-11-02, Luke Closs <[EMAIL PROTECTED]> wrote:
> >
> > Also, yesterday Test::WWW::Selenium was uploaded to CPAN, so Selenium
> > can now be driven by perl!
>
> Test::WWW::Selenium seems interesting, but I could use an example i
--- Mark Stosberg <[EMAIL PROTECTED]> wrote:
> > http://openjsan.org/doc/t/th/theory/Test/Simple/0.21/index.html
> >
> > I've been using it and once you get it set up, it's fairly straight
> > forward. You can see a sample in my journal:
> > http://use.perl.org/~Ovid/journal/27229
>
> Interesti
The whole scratchpad is doomed and will be scratched RSN (see pdd20
instead). A patch with immanent changes is at
http://perlcabal.org/~lt/pad.diff
but the patch doesn't properly reflect deleted files - if you like to
experiment, please svn rm the deleted files:
D src/lexical.c
D
On Nov 28, 2005, at 22:37, Chip Salzenberg wrote:
PS: I'd forgotten the lex opcodes used to follow the *call stack*.
My unholy $DEITY, they were even more broken than I remembered.
Yes. And have supported hacks that were far beyond anything dubbed as
damian-ish (pdd20).
Re: tcl - it's
the parrot directory structure is large and a bit disorganized.
let me give you some examples:
* build_tools/, util/, and tools/*/ each contain utility perl
scripts. these should be grouped together under tools/, which
already contains subdirectories
* there are multiple dirs containing C sourc
Hi Jerry,
I'm just curious, I don't mean to criticize your ideas. Just, give
some "why"s for the "should"s.
On 11/29/05, jerry gay <[EMAIL PROTECTED]> wrote:
> the parrot directory structure is large and a bit disorganized.
> let me give you some examples:
> * build_tools/, util/, and tools/*/ e
On 11/28/05, Luke Palmer <[EMAIL PROTECTED]> wrote:
> Hi Jerry,
>
> I'm just curious, I don't mean to criticize your ideas. Just, give
> some "why"s for the "should"s.
>
no worries--this isn't criticism, it's feedback.
> On 11/29/05, jerry gay <[EMAIL PROTECTED]> wrote:
> > the parrot directory s
On Mon, Nov 28, 2005 at 04:45:33PM -0800, jerry gay wrote:
> i propose reorganizing the tree to improve clarity and cohesion.
Reorganization would be good at this point, but should be undertaken
cautiously so as to minimize unpleasantness.
* I can't find a rationale for putting both 'imcc' and 'c
On Mon, Nov 28, 2005 at 04:45:33PM -0800, jerry gay wrote:
> the parrot directory structure is large and a bit disorganized.
> let me give you some examples:
> * build_tools/, util/, and tools/*/ each contain utility perl
> scripts. these should be grouped together under tools/, which
> already
On Mon, Nov 28, 2005 at 05:37:19PM -1000, Joshua Hoblitt wrote:
> On Mon, Nov 28, 2005 at 04:45:33PM -0800, jerry gay wrote:
> > * the editor/ directory contains files for text editors and has
> > a generated makefile. there is no reason for this to be a make
> > target. a perl script should be
jerry gay <[EMAIL PROTECTED]> wrote:
> the parrot directory structure is large and a bit disorganized.
> let me give you some examples:
Agreed. I find this confusing sometimes, not being intimately familiar
with all of parrot.
> i propose reorganizing the tree to improve clarity and cohesion.
> h
22 matches
Mail list logo
