The translation is actually rather easy. It's just a bunch of RegEx for parsing and rules for understanding. The limitations of cfscript are perfect here as there are not many rules. The only thing would be the loops that are available in cfscript but do not exist in standard cf. Also, if someone is taking advantage of how cfscript handles loops (check per loop instance), they will probably have a problem with the normal from/to cfloop.
If you want it to be a cfeclipse feature then I'd need someone who is more knowledgeable in that area. It's easier as a cfbuilder extension though. I think that more specifications are needed. p.s. please don't flame here. Tech talk only. Flames on the cf-community list. Thanks On Thu, Apr 7, 2011 at 7:20 PM, Jeff Gladnick <[email protected]>wrote: > > I actually don't hate cfscript, but I do hate that we have both tags and > script based syntax for CFML. And since it started off as tags, I firmly > believe that's the way it should stay. > > I understand lots of people feel differently, but it really sucks (for me) > seeing all the new great open source projects being released in cfscript. > > Therefore I have created a $1000 bounty (I have pledged $250) to the first > developer who can deliver a working cfscript --> cftag based parser for > eclipse. > > http://www.pledgebank.com/CFScriptSucks > > People can still write in cfscript if they want to, but people who feel > like me won't have to deal with it anymore. > > Please post flames below. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:343612 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
