It's important to note that if you do this, you sacrifice the ability to
have "standard" Fusedoc tools operate on your Fusedoc'd code. While I don't
see this as a problem with test harnesses, I would be cautious about doing
it in permanent code.
Hal Helms
== See ColdFusionTraining.com for info on "Best Practices with ColdFusion &
Fusebox" training ==
-----Original Message-----
From: Jeff Peters [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 10, 2001 9:47 PM
To: Fusebox
Subject: Harness 1.04
Based on feedback from some Fuseboxers, I've updated Harness to treat "==>"
as
equivalent to "-->". The allows you to use ==> as the input attribute
indicator in your Fusedocs, thus preventing Studio from miscoloring your
Fusedoc due to the "end of comment" interpretation of --> in its syntax
coloring code. Of course, you can still use -->, as that is Hal's official
spec.
The new version is available in "Grok's Goodies" at www.GrokFusebox.com
Have fun!
- Jeff
P.S. This suggestion came out of conversation on the #fusebox IRC channel.
The
community strikes again...
==============================================================
| Jeffrey S. Peters | "Specialization is for insects." |
| [EMAIL PROTECTED] | - Lazarus Long |
| PGP key for Jeffrey S. Peters at ldap://keyserver.pgp.com |
==============================================================
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
