We use the shorthand @@ pretty much everywhere unless we need to
specify encoding or formatting. We use <@var> a lot when generating
files - as was pointed out, sometimes you need the space on the front
of the @@ to get through the parser, but then you don't want that
space char in the file.
In general the language is fairly verbose, and it is fairly easy to
have metatags nested six or seven times deep (ever written a function
call with a dozen parameters in text? it can easily fill half a
screen with solid text). My choice is readability (ie, it can be
understood and supported easily) over ultimate speed. Generally our
code is commented and has plenty 'white space' (empty lines, spaces
etc) to make it easier for the programmers to figure out what is
going on. If you are on a bug hunt through something written by a
team of people a year or two ago, there is no point in it being any
harder than it has to be.
We've run everything cached, so the only performance hit is the first
time the code hits the parser. After that, writing styles don't matter.
As far as 'bugs' go, we scope and quote _everything_. If you do that,
the language pretty much works as advertised.
J.
On 09/02/2007, at 6:11 AM, William M. Conlon wrote:
I see the shorthand as a developer aid,
WITH IMAGINATION
Planning, Implementation and Management of Web Applications
Level 1, 44 Miller Street North Sydney NSW Australia 2060
phone + 612 9929 9229 fax + 612 9460 4770
web - www.wi.com.au email - [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by ESVA, and is
believed to be clean.
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
