in reply to How about class Foo {...} definition for Perl?
The syntax seems fairly nice and more like 'standard' OO
One problem I see with this sort of thing, though, is that without completely parsing the whole filtered source file there are ways in which to confuse it. I had a quick look at the source code and it seems that if you were to put some of the things which the filter is replacing (eg the sub declerations) inside a quoted string they would still be replaced even though they clearly shouldn't. I know this is not likely to happen normally, but it would be a nasty gotcha if it did.
It all comes down to the difficulty in parsing perl. I did something which involved inventing a bit of new notation for perl once. It worked ok, provided I avoided anything which would confuse it. It suffered this same problem though.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: How about class Foo {...} definition for Perl?
by gmpassos (Priest) on Jan 17, 2004 at 23:43 UTC | |
by hhdave (Beadle) on Jan 18, 2004 at 00:39 UTC |