Re: Trying not to re-invent the wheel

1999-11-17 Thread Andy Wardley
On Nov 14, 5:00pm, Leslie Mikesell wrote: This means that you can't easily make nested sub-pages without knowing ahead of time how they will be used, and worse, if you get an error in step 3 of generating a page you can't undo the fact that steps 1 and 2 are probably already on the user's

Re: Trying not to re-invent the wheel

1999-11-14 Thread Rasmus Lerdorf
On Fri, 12 Nov 1999, Jim Winstead wrote: On Nov 10, Mark Cogan wrote: At 10:10 AM 11/10/99 -0800, Ian Mahuron wrote: I may implement IF/LOOPS/etc.. but not until I see the need. Those introduce more complex problems. And they are, of course, inevitable with almost any templating

Re: Trying not to re-invent the wheel

1999-11-14 Thread Leslie Mikesell
According to Rasmus Lerdorf: Those introduce more complex problems. And they are, of course, inevitable with almost any templating system. You know, PHP was once just a templating system. [...] Then I figured it would be a good idea to add stuff like IF/LOOPS/etc so I could

Re: Trying not to re-invent the wheel

1999-11-14 Thread Rasmus Lerdorf
According to Rasmus Lerdorf: Those introduce more complex problems. And they are, of course, inevitable with almost any templating system. You know, PHP was once just a templating system. [...] Then I figured it would be a good idea to add stuff like IF/LOOPS/etc so I

RE: Trying not to re-invent the wheel

1999-11-12 Thread Sam Tregar
I've written up a few test benches for HTML::Parser.. it works ok, but it's not as fast as I would like it to be. IS there some reason you don't just use HTML::Mason? Patient: My tooth aches. Doctor: Is there some reason you haven't replaced your teeth with dentures? -sam

RE: Trying not to re-invent the wheel

1999-11-12 Thread Ian Mahuron
I've decided to go with Mason.

Re: Trying not to re-invent the wheel

1999-11-12 Thread Jim Winstead
On Nov 10, Mark Cogan wrote: At 10:10 AM 11/10/99 -0800, Ian Mahuron wrote: I may implement IF/LOOPS/etc.. but not until I see the need. Those introduce more complex problems. And they are, of course, inevitable with almost any templating system. Jim

Re: Trying not to re-invent the wheel

1999-11-11 Thread Randal L. Schwartz
"Joshua" == Joshua Chamas [EMAIL PROTECTED] writes: Joshua What Matt brought up is right. Eewww. Whenever I read "matt" and "w(right)" in the same sentence, all sorts of alarms go off. Sorry. :-) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 [EMAIL

Trying not to re-invent the wheel

1999-11-10 Thread Ian Mahuron
Hi guys gals. I'm writing a mod_perl handler for a ColdFusion'esque embedded scripting language... I was wondering what the quickest (performance wise) way to parse through the HTML is. Embperl documents show that it requires HTML::Parser, though I can't seem to find where it uses this module

Re: Trying not to re-invent the wheel

1999-11-10 Thread Sam Tregar
On Wed, 10 Nov 1999, Ian Mahuron wrote: The code in HTML::Template may work.. though it seems that it would be very slow. Actually, I like to think it's some pretty fast code... Of course, that's because it's only looking for TMPL_* tags, and it's allowing them to break all kinds of HTML

RE: Trying not to re-invent the wheel

1999-11-10 Thread Ian Mahuron
As per someone's suggestion I'll ellaborate on what's in the HTML... Insert code for advertisment (there's 1,000's of different ads on the site.): ADVERTISMENT id=252 Insert news scroller: NEWS_ITEM id=92834 bgcolor="#0066FF" There will be at least 50 similar tags.. so I'm not parsing for

RE: Trying not to re-invent the wheel

1999-11-10 Thread Christian Gilmore
PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ian Mahuron Sent: Wednesday, November 10, 1999 1:10 PM To: Ian Mahuron; ModPerl Subject: RE: Trying not to re-invent the wheel As per someone's suggestion I'll ellaborate on what's in the HTML... Insert code for advertisment (there's 1,000's

Re: Trying not to re-invent the wheel

1999-11-10 Thread Eric L. Brine
There will be at least 50 similar tags.. so I'm not parsing for just couple of tags like HTML::Template.. I may implement IF/LOOPS/etc.. but not until I see the need. It might be too late to do this, but what if you convert everything to one tag. I can better explain by example: Instead of

RE: Trying not to re-invent the wheel

1999-11-10 Thread Tobias Hoellrich
I don't know, if you have to stick to the tags as described below, but if you don't have to you may want to take a look at a custom Apache::SSI subclass which can do all this stuff for you and no perl-based HTML parsing is involved: !--#ADVERTISMENT id=252 -- Tobias At 10:10 AM

RE: Trying not to re-invent the wheel

1999-11-10 Thread Jason Bodnar
I believe there are a couple of HTML parsers out there. In the Perl News email sent out a couple of days ago there was one that caught my eye. I believe it was an XS implementation so it should be very fast. I'm not an XML expert but you might want to try the XML parser. It's also a perl

Re: Trying not to re-invent the wheel

1999-11-10 Thread Gisle Aas
"Christian Gilmore" [EMAIL PROTECTED] writes: I found that writing my own parser to fit my specific need was far and away the fastest thing I could do. It really depends upon your specific application. HTML::Parser is nice if you want to see the structure of the document your parsing but is

Re: Trying not to re-invent the wheel

1999-01-16 Thread Robin Berjon
At 18:53 12/11/1999 -0500, Rasmus Lerdorf wrote: You know, PHP was once just a templating system. I had special tags that I replaced with the output from the business logic I wrote in C in order to avoid needing to recompile my code just to tweak the HTML. Then I figured it would be a good idea