all this cfscript talk...
can I just have a step debugger...and breakpointsand watches
pretty please?
On 5/9/06, Gary Menzel [EMAIL PROTECTED] wrote:
Damn good suggestion.
I had previously suggested the idea of having another CFSETTING attribute
(something like lang) to set it as a
It might be better get Adobe to update the cfscript tag to include
lang=ecmascript that way it opens to door to lang=java or whatever
your favourite language that has a java compiler for it. Thus by
default lang=cfscript and then you're open to mix and match
scripting languages to you hearts
You can do (almost) anything.NET, so in the same vein, if they do make
java bytecode compilers for other languanges, I think they could wire
those in just fine.
Support wise, the API documentation for different languages could be
auto generated... I'm sure javadoc would make short work out
That is an unreasonable comment, Mark.We aren't asking for something new to be added - we are just asking for something that already (almost) exists to be made standard.MM introduced CFSCRIPT in the first place (maybe it was because someone asked for it - I dont know) - but they should now SUPPORT
Agreed. One of the problems with CFSCRIPT is that it is not ECMAScript
compliant. When switching between JavaScript and CFSCRIPT, it can
often get confusing - especially when you are dealing with conditions.
I imagine this will be the same case with developers who shift between
AS3 and CFSCRIPT.
That way you could picklanguages like you pick underwear (hopefully one for each day of theweek).Now now Mark, don't you know ya can wear underwear 4 times before washing, frontwards, backwards, inside-out frontwards, inside-out backwards.
M@Who can't quite remember what song/thing that comes
I think a lot of the reason we haven't "seen much"
Flex/Flash work out there was the high cost for Flex (1). Flex 2's pricing model
should help there quite a bit. There are still a lot of people under the
impression that "flex will cost". It's not quite true. If you want to, you will
be
Dale,Money isn't everything bro. At this point flexibility is my biggest hurdle. There's plenty of work in Australia at the moment. Heck there is a CF7 install contract going in Brissy. Very tempting. There's plenty of work out there, not all of it is on the boards either.
$60k contract and a
I have to say i dont mind using the tag-based syntax for writing code. I would argue rather than making CF script ECMA compliant they should make the tag-based syntax XML valid! Who wants to write in the ugly Perl-like syntax of Php ? And its not so much writing it as it is reading other people's
Two things wrong with Tag based code.
1. Other developers when they see ColdFusion code hate it and immediately
dismiss it as not a real language
2. You need to write about double the amount of code every time
cfloop index=i from=1 to=10
/cfloop
for (i=1; i=10; i++) {
}
See the differences
everything has its place, and the tag syntax does make some tasks allot
easier. That sais, for those people who prefer the script syntax it does
make it a pain when you have to break out of the script block to do
something and then open it up again to keep going.
Anything you do with tag code
I should have been more specific..ECMA compliant syntactically.So - I think we are on the same page.I actually don't really go in for the compliance at that object level (as not all environments would be able to support all the same objects). If they did - we would only need one language!
So -
12 matches
Mail list logo
