Re: Tinderboxens

Sorry for the late response, I've been out of town and it took me a while to catch up on p6i. On 7/18/03 8:36 PM, "Joshua Hoblitt" <[EMAIL PROTECTED]> wrote: [SNIP] >> it's got some error identification issues, This is something I plan to work on more, the regexps that define sucuess/failure (in

Re: The Perl 6 Summary -- preprocessors

> grammar Grammars::Languages::C::Preprocessor { > rule CompilationUnit { > ( | )* > } > > rule Directive { > ( Include >| Line >| Conditional >| Define > ) * > } > > rule Hash { /^\s*#\s*/ } > rule Include {...} > rule Line {...

Re: The Perl 6 Summary -- preprocessors

"Austin Hastings" <[EMAIL PROTECTED]> > > I.e. is it just an input stream filter? > Doubtful. > > Do you want to do this at the grammar level, or the file level? > > If you want it at the file level, you C a translator (ooh! my > first p6 idiom!) to the file handle. > > If you want it at the gramma

Re: The Perl 6 Summary -- preprocessors

--- Dave Whipp <[EMAIL PROTECTED]> wrote: > "Austin Hastings" <[EMAIL PROTECTED]> wrote: > > $.source = (new > Grammars::Language::C::Preprocessor).open($source); > > I find myself wondering if this is covered by the P6 equiv of > TieHandle. > I.e. is it just an input stream filter? > Doubt

Re: The Perl 6 Summary -- preprocessors

--- David Storrs <[EMAIL PROTECTED]> wrote: > On Mon, Jul 21, 2003 at 12:19:11PM -0700, Austin Hastings wrote: > > > Likewise: > > > > my $fh = open " > > > $fh =~ / > = Grammars::Languages::Runoff::tbl(input_method > >= Grammars::Language::Runoff::eqn(input_method > >

Re: building a watchdog

> "Darren" == Darren Chamberlain <[EMAIL PROTECTED]> writes: Darren> * Randal L. Schwartz [2003-07-21 13:21]: >> It occurs to me that that if I wanted to build a health check watchdog >> for my system (a script that executes at regular intervals to ensure >> proper operation), that the Test::

Re: The Perl 6 Summary -- preprocessors

"Austin Hastings" <[EMAIL PROTECTED]> wrote: > What you really want is to be able to "chain" grammars: > > > my $fh = open " > $fh =~ //; > > grammar Grammars::Languages::C { > method init { > SUPER::init; > > $.source = (new Grammars::Language::C::Preprocessor).open($source); > } > .

Re: Small perl task for the interested

Josh Wilmes <[EMAIL PROTECTED]> wrote: >> .c$(O) : >> $(PERL) tools/dev/cc_flags.pl $(CC) $(CFLAGS) ${cc_o_out}$@ -c $< > > I would go a bit further, and create a tools/build/compile, tools/build/ > link_executable, tools/build/link_library, etc. > > Take all the flags out of the makefile

Re: [perl #23027] [PATCH] Per-c-file flag handling in make

At 8:26 PM + 7/17/03, Lars Balker Rasmussen (via RT) wrote: I've added a way to add or remove options on a per-c-file basis. Right now all it does is make sure that tsq.c won't be affected by Configure.pl --optimize, and that the amounts of silly warnings is reduced (by removing -Wformat-nonli

Re: The Perl 6 Summary -- preprocessors

On Mon, Jul 21, 2003 at 12:19:11PM -0700, Austin Hastings wrote: > Likewise: > > my $fh = open " > $fh =~ / = Grammars::Languages::Runoff::tbl(input_method >= Grammars::Language::Runoff::eqn(input_method > = IO::Gunzip)))>/; Very cool. Assuming this ran succe

Re: The Perl 6 Summary -- preprocessors

--- Dave Whipp <[EMAIL PROTECTED]> wrote: > "Piers Cawley" <[EMAIL PROTECTED]> wrote > > Parsers with Pre-processors > > I didn't quite understand what Dave Whipp was driving at when > > he talked about overloading the "" pattern as a way of doing > > preprocessing of Perl 6 patterns. I didn't und

[perl #23076] Parrot Array

# New Ticket Created by Andy Bussey # Please include the string: [perl #23076] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=23076 > I assume it should be possible to push something on to an empty Array, but it doesn't wor

Re: building a watchdog

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Randal L. Schwartz [2003-07-21 13:21]: > It occurs to me that that if I wanted to build a health check watchdog > for my system (a script that executes at regular intervals to ensure > proper operation), that the Test::* mechanisms would be pretty i

Memory system questions

Hello, While reworking the IO-system I get deeper in the memory system than I wanted to. So I have some questions: * Is there a way to trace only a part of the rootset? pobject_lives only adds an element to the root-set. But creation of the rootset and tracing of PMCs are done (as far as I ca

Re: building a watchdog

My initial thought would be simply to have a series of test programs to verify everything that you need. Then set up a cron job and just run 'em through Test::Harness and pipe the output to your favorite mail program. perl -MTest::Harness -e 'runtests(glob "/path/to/tests/*.t")' 2>&1 | mail

Re: [perl #23064] [PATCH] Fix copyright notices

On Sunday, July 20, 2003, at 10:30 AM, Josh Wilmes (via RT) wrote: Here's a first pass, just changing any existing "when this is determined" or YAS messages to TPF. I won't apply this one myself as I lack the legal experience to understand whether it is properly done. It's passed muster at the

building a watchdog

It occurs to me that that if I wanted to build a health check watchdog for my system (a script that executes at regular intervals to ensure proper operation), that the Test::* mechanisms would be pretty ideal for checking the results and reporting the proper errors. I can't be treading new ground

Re: The Perl 6 Summary -- preprocessors

"Piers Cawley" <[EMAIL PROTECTED]> wrote > Parsers with Pre-processors > I didn't quite understand what Dave Whipp was driving at when he talked > about overloading the "" pattern as a way of doing preprocessing of > Perl 6 patterns. I didn't understand Luke Palmer's answer either. He

Re: Events

At 1:09 PM -0400 7/20/03, Michal Wallace wrote: On Sun, 20 Jul 2003, Dan Sugalski wrote: >It would be entirely possible for Parrot (or a Parrot library) to >use AIO at a low level, without introducing interrupts to the VM layer. Sure. But what'd be the point? Adding in interrupts allows a numb

Re: The Perl 6 Summary

Adam Turoff <[EMAIL PROTECTED]> writes: > On Mon, Jul 21, 2003 at 03:20:26PM +0100, Piers Cawley wrote: >> Acknowledgements, Announcements and Apologies >> First of all, I plead insanity for my mistake of last week's summary. >> PONIE does not stand for 'Perl On New Internal Architecture',

Re: The Perl 6 Summary

On Mon, Jul 21, 2003 at 03:20:26PM +0100, Piers Cawley wrote: > Acknowledgements, Announcements and Apologies > First of all, I plead insanity for my mistake of last week's summary. > PONIE does not stand for 'Perl On New Internal Architecture', it > obviously stands for 'Perl On New Im

The Perl 6 Summary

Perl 6 Summary for the week ending 20030720 Welcome back to an interim Perl 6 Summary, falling as it does between two conference weeks; OSCON and YAPC::Europe. For reasons involving insanity, a EuroStar ticket going begging, and undeserved generosity I shall be bringing my conferenc

Re: Abbreviation

Vladimir Lipskiy wrote: In /parrot/docs/jit.pod: "For moving registers from processor to parrot and vv, the B functions have to be implemented." what does "vv" stand for? vice versa (from processor to parrot and back) leo

hey how are you

This message is in HTML format. 5204.auf

Lower your payments

This message is in HTML format. 2273.rpd

Re: Abbreviation

On Mon, Jul 21, 2003 at 10:28:26AM +0300, Vladimir Lipskiy wrote: > In /parrot/docs/jit.pod: > > "For moving registers from processor to parrot and vv, the > B functions have to be implemented." > > what does "vv" stand for? Vice versa, I presume. -- Lars Balker Rasmussen

Re: [WIP PATCH] core.ops split-up

"Brent Dax" <[EMAIL PROTECTED]> writes: > Anyway, a corrected patch that fixes the trans.t errors is up at > . Uh, there's still no "+inline op sin" in that file? > If it doesn't > apply the first time, try splitting the patch into several