Or thought of in a simpler way:
The Cold Fusion parser takes the CFML tags OUT of the page, and replaces them with the
HTML that the tags generated.
The "NEWLINE" at the end of each CFML line is *NOT* considered part of the CFML tag
(obviously, only the parts in < > are part of the tag) and the "NEWLINE" is *NOT*
removed by the parser. Thus:
<p>
<cfthis>
<cfthat>
<cfthese>
<cfthose>
<hr>
becomes:
<p>
<hr>
At 09:27 AM 1/31/01 +0000, Paul Johnston wrote:
> > >
> > > > Thats very interesting, because doing a view source indicates
> > > > that they are
> > > > using CF:-)
> > > >
> > > > I mean how many other scripting languages generate that much
> > > whitespace!
> > > >
> > >
> > > Erm...
> > >
> > > Loads of languages generate that much whitespace!
> >
> > Which ones?
>
>Perl (if badly written), PHP (if badly written), ASP (if badly written), CF
>(if badly written), Mason (if badly written), and everything else under the
>sun (if it's badly written). CF, however is a bit more interesting...
>
>The point about CF is that it uses the approach of "Anything written in CF
>changes to whitespace when processed" as a default, instead of treating CF
>as a programming language and compiling etc (prepare to flame me...).
>That's what produces the whitespace. This can of course be turned off, and
>can mean faster page loading. The CFML processor is effectively only a
>parser (a fast one, but still a parser) so any other language that is parsed
>like this will produce similar output.
>
>Paul
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
