is indicative of a structure problem. Parsers have been around pretty much
as long as computers have been and techniques for building parsers are
pretty well established. Structural requirements like this are pretty rare.
If they built coral without a proper parser, what else is done improperly?
Scares me off quite a bit.
And besides, what about code like this:
<tr bgcolor="<cfif condition>red<cfelse>green</cfif>">
It's horrible code that I wouldn't write in a new app but it exists in
pretty much every app i'm maintaining.
Sam
----------------------------------------------
Blog: http://www.rewindlife.com
Chart: http://www.blinex.com/products/charting
----------------------------------------------
-----Original Message-----
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 7:32 AM
To: CF-Talk
Subject: Re: Another CFML app server...
Michael Dinowitz wrote:
> They emailed me directly and we were going to talk. After some
investigation, I
> found at least one major problem with it. All CF code has to be on its own
line,
> one tag per line. I think that describes maybe 1 persons code in all the
> community.
ReplaceNoCase(template, "<cf","#chr(13)##chr(10)#<cf","All")
> I'll interview them but they don't 'feel' like something terribly big.
Neither did NewAtlanta two years ago.
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
