Disney!

[Owen Densmore]

We're off to Disney. At farina, a great pizza joint on abq. Back in a week. One last word: CofeeScript. Try it, you'll like it.

-- Owen

[Peter Robert Guerzenich Small]

Re: Coffee Script

The question is: how do you debug it?

On Jun 7, 2012, at 7:04 PM, Owen Densmore <oden...@gmail.com> wrote:

>
> We're off to Disney. At farina, a great pizza joint on abq. Back in a week. One last word: CofeeScript. Try it, you'll like it.
>
> -- Owen
>

> --
> You received this message because you are subscribed to the Santa Fe Complex "discuss" group.
> To post to this group, send email to dis...@sfcomplex.org
> To unsubscribe from this group, send email to
> discuss+u...@sfcomplex.org
> For more options, visit this group at
> http://groups.google.com/a/sfcomplex.org/group/discuss

[Robert J. Cordingley]

...and since you mention it: Disney fans should watch for the release of
'Wreck it Ralph':

http://disney.go.com/wreck-it-ralph/?cmp=wdsmp_wir_url_dcomwreckitralph

due out later this year. Disclosure: son Chris is one the Character
Animators and says "It's a pretty good movie."

Robert C

[Greg Sonnenfeld]

I hope its not set on mars....

****************************
Greg Sonnenfeld

[Bruce Sherwood]

Not clear that debugging is particularly worse with CoffeeScript than
with other languages. I have tripped over some things but ascribed it
to having not really studied the language. I've just gone with brief
summaries of how it differs from JavaScript.

At glowscript.org, click on Example programs where you'll see a few
examples of pairs of identical programs, one element of the pair in
JavaScript, one in CoffeeScript. GlowScript uses the ACE text editor
which can cater to CoffeeScript but I haven't yet set that up, so when
writing CoffeeScript I miss the useful worker-thread hints of problems
that I get when editing JavaScript.

In these pairs (and the Rug example that is only in CoffeeScript), you
may agree that the CoffeeScript code is significantly cleaner. It's
sure easier to write, too.

Bruce

P.S. To run the GlowScript examples, which use WebGL, you need to have
a WebGL-enabled browser. See the Help at glowscript.org for details.

[Peter Robert Guerzenich Small]

The issue with debugging coffee script is that you can't debug coffee script.
When you set a breakpoint in the code to step through it, you are stepping through the generated javascript, not coffee script.

[Bruce Sherwood]

Ah. Right. I didn't realize that "debugging" was being meant in the
technical sense, as opposed to just the usual problems of getting a
program to work.

It sounds like a solvable problem, if for example comments with
original line numbers were added to the CoffeeScript code before
conversion to JavaScript.

Bruce

[Joshua Thorp]

But in practice is this really such a problem? I suppose the biggest problem is it requires you to be debugging in Javascript which is not so much fun when you would prefer to be in CoffeeScript. But I don't think that is what you are getting at?

--joshua

[Gary Schiltz]

I can't imagine debugging generated code to figure out what the problems with my source code is. Kind of like stepping through machine code when I really want to step through my C code, or through Java bytecode instead of the Java source (of course I realize that Javascript is a lot higher level, but still much better to see the source in the same language that the program was written in). But then, I practically live in the debugger while writing Java (make a few changes and step through the source code to make sure it's actually doing what I meant for it to do).

;; Gary

[Peter Robert Guerzenich Small]

There may be a solution to this problem: Source Map. It looks like it might support debugging the actual coffee script. I haven't dug into it yet, but it looks promising:

https://www.youtube.com/watch?feature=player_embedded&v=-xJl22Kvgjg

P