Im guessing people wnat this to have OPTIONS right? because, why have both type of scriptings? Stick to tag based syntax and just trow us more tags :) (and yes, I am a very much "why" guy)

I'm the opposite. I'm at the point where I want Adobe to let me do all of my CF code as "cfscript" that is unless I'm specifically mingling my CF code with javascript or html. Come on, let us have .cfs files!

I noticed that at the keynote and I'm REALLY HOPING to get all cfscript syntax. The tag based syntax makes no sense for writing cfcs.

Yeah -- why don't we just get rid of tags altogether and do everything in scripts -- then we can be just like PHP! ;-)

it would be nice to have some good documentation for cfscript as well.. i remember having to hunt and guess how code inside of cfscript. it was hard to find really good documentation on how to implement functionality within cfscript.

I would love to see that also

<cfscript language="ActionScript" strict="true">
private var name:String = 'Dale';
private var employee:Query = new Query();

employee.statement = 'select * from employee where name = %1';
employee.setParam(name, 'String');
employee.execute();

for (var i:int = 0; i++; i < employee.result.recordCount) {
writeOutput('Hello ' + employee.result[i].fullName);
}
</cfscript>

@Paul... learn Flex / Actionscript and you will start to understand. Or learn JS and DOM and that might help. CF started (in some peoples opinion) a good thing with version 5 and script. Yet, the feature set has always been limited. This means the full argument for the benefits (not exclusive use) of script cannot be made. We do get more and more with each version and the arguments are getting better as the script gets better.

@Dale... I think there is still a good place for tags. Uniquely the concept that CFCs are not a place where you should require tags is a good thing IMO. Tags are great for view based logic.

I have heard the argument about actionscript in Coldfusion far too many times, and the fact of the matter is that in my personal opinion it is overkill.

Coldfusion is a scriptin language compiled to java, and in my expereince it would be far easier to adopt the JSP scripting language or Java style rather than a hashed version of something that adds more complexity.

In Dales example I would prefer to see this instead

<cfscript>
private String name = 'Dale';
private Query employee = new Query();

//Although from Dales example this would be a struct not a query object
employee.statement = 'select * from employee where name = %1';

employee.setParam(name, 'String');
employee.execute();

for (var i:int = 0; i++; i < employee.result.recordCount) {
writeOutput('Hello ' + employee.result[i].fullName);
}
</cfscript>

I am fully against Actionscript in Coldfusion, I believe it is better to adopt a more logical method that is more common in JSP, Java and .Net than go with something that was pulledout of hat just to be different.

And besides, going more like Java means no preprocessing and less translation.

@pete, thanks I think i did stumble across that when i had started using cfscript. it was a great help, but i was looking for more info on the cfml things like query and such.

does charlie have this listed on his resource list? i took a look, but i didn't see it.