Though I still use often @@scope$varname shorthand, there are at least two cases that come to mind where the shorthand fails me: * use of ENCODING or FORMAT attributes * in some contexts when the '@@' is not separated from the preceding characters. In fact, the shorthand format should be specified as ' @@scope$varname'.
Also, I imagine that my proposed <@OPTIMIZE> tag (see list archive about two weeks ago) could be problematic with the shorthand. I see the shorthand as a developer aid, not a run-time optimization (fewer characters). [Actually I suspect if we had a switch to ignore shortcuts, and only honor the formal <@VAR SCOPE="scope" NAME="varname">, the parser would be faster.] What I would ask for in the Studio is smart code completion, that allowed a developer to type the shorthand, and get the formal tag. -- Bill ---------- Original Message ----------- From: "Shane Pearlman" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thu, 8 Feb 2007 10:54:40 -0800 Subject: RE: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 - Syntax Errors > We have used @@ for years with no issues that we are aware of. > Though we are religious about making sure to use a scope with everything... > @@request$myvar .... > > Shane Pearlman > 831.345.7033 > S&P, Inc. > > -----Original Message----- > From: David Green [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 08, 2007 10:31 AM > To: [email protected] > Subject: Re: Witango-Talk: Upgrading from Witango 5.0 to Witango 5.5 > - Syntax Errors > > When exactly were we as developers told not to use the @@ shorthand? > I missed that update and have been using it for the past 8 years. > I just checked with the 5.5 Programmer's Guide and it still gives > examples using that shorthand. > > Just curious... > > David Green > [EMAIL PROTECTED] > Web Services > Systems Insight, Inc. > http://www.systemsinsight.com/ > > John McGowan wrote: > > Due to unpredictable behavior related to the interpretation of the @@ > > notation in Tango, we stopped using it a long time ago. I can't comment > > on 5.0 vs 5.5. support, because it's something that I started getting > > away from back on Tango 2000 > > > > /John > > > > On 2/7/07, *Jason Pamental* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Adam, > > > > I have no comments for or against the ( instead of [ trick - but if > > it works that certainly helps, doesn't it? I would guess it has more > > to do with the code shorthand not being handled properly though - > > and could also be handled by a search and replace. I always write > > things out a bit more, like: > > > > <@var request$exampleArray[<@var request$rowCounter>,FieldName]> > > > > You might try doing a replace on one file and see if it works. It's > > certainly more 'correct' than using the parentheses, although I > > really don't know if that's going to help. > > > > Good luck with it! > > > > Jason > > > > ----- > > > > Jason Pamental > > Director of Web Services > > North Sails > > > > Office: 401.643.1415 > > Fax: 401.643.1420 > > Mobile: 401.743.4406 > > Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > > > > > > > On Feb 7, 2007, at 4:26 PM, Adam Leisring wrote: > > > >> Thanks for the info. Jason. I've actually figured out a > >> work-around, but it's not one that I feel comfortable implementing. > >> > >> The issue seems to occur in IF actions (not metatags), I've pasted > >> examples below: > >> > >> Non-working example in 5.5 - working in 5.0: > >> @@request$exampleArray[@@request$rowCounter,FieldName] > >> > >> Working example in 5.5 - not tested in 5.0: > >> @@request$exampleArray(@@request$rowCounter,FieldName) > >> > >> You'll notice that all I've done to fix the issue is replace the > >> [] brackets with () parenthesis. I've checked Witango > >> documentation, this is not correct syntax, but works none-the-less. > >> > >> It seems like the Witango interpreter is getting hung up on [] > >> used in extracting array data in IF actions... maybe related to > >> the CDATA encapsulators? > >> > >> Has anyone encountered an issue like this? Can someone from the > >> Witango team provide any insight? This issue affects around 20% > >> of our applications and has thrown a wrench into our conversion > >> timeline! > >> > >> Our environment is a Windows 2000 Advanced Server using Witango > >> 5.5.20 and a Pervasive 9.5 Database. > >> > >> Thanks to any help anyone can provide! > >> > >> Adam Leisring > >> Fischer Homes, Inc. > >> > >> > >> > >> >>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >> 02/06/07 12:08PM >>> > >> Adam, > >> > >> The only major 'gotcha' I encountered was making sure that all > >> places where I used 'encoding=multilinehtml' were change to > >> 'encoding=multiline'. Otherwise I don't think I had any problems. > >> Things to look at though would also be customizations you may have > >> made to the witango.ini file - like default scope for variables. > >> > >> It would help to know the server platform though, and any other > >> details you can think of. If you look at two or three of the files > >> that are producing errors you might find a common thread. > >> > >> Hope that helps- > >> > >> Jason > >> > >> ----- > >> > >> Jason Pamental > >> Director of Web Services > >> North Sails > >> > >> Office: 401.643.1415 > >> Fax: 401.643.1420 > >> Mobile: 401.743.4406 > >> Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >> > >> > >> > >> > >> On Feb 6, 2007, at 11:19 AM, Adam Leisring wrote: > >> > >>> Hello everyone, > >>> > >>> We're in the process of upgrading our Witango Server from 5 to > >>> 5.5 and we've encountered an odd issue. Applications that work > >>> properly in the 5 environment are throwing Syntax errors. > >>> Specifically, it deals with 'Missing closing brackets' and > >>> 'Missing quote at the end of the statement' kinds of problems. > >>> Again, these applications work without issue in the 5 environment. > >>> > >>> Has anyone encountered something like this? Am I missing a > >>> configuration option? Is there a conversion application I should > >>> run against the Witango 5 applications to bring them up to 5.5? > >>> > >>> Any help is greatly appreciated! > >>> > >>> Thanks, > >>> Adam Leisring > >>> Fischer Homes, Inc. > >>> > ________________________________________________________________________ > >>> > >>> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > >> > >> > ________________________________________________________________________ > >> TO UNSUBSCRIBE: Go to > >> http://www.witango.com/developer/maillist.taf > >> > ________________________________________________________________________ > >> TO UNSUBSCRIBE: Go to > >> http://www.witango.com/developer/maillist.taf > > > > > ________________________________________________________________________ > > TO UNSUBSCRIBE: Go to > > http://www.witango.com/developer/maillist.taf > > > > > > > > > > -- > > John McGowan > > Seven A C Consulting, Inc. > > > > ________________________________________________________________________ > > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ------- End of Original Message ------- ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
