5 comments
Comment actions Permalink

Hello Donald,

Shouldn't we wait until the language is actually designed and implemented
before starting work on a plugin? :)

Those Google guys are at it again:

http://code.google.com/p/noop/

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello Donald,

Shouldn't we wait until the language is actually designed and implemented
before starting work on a plugin? :)

Those Google guys are at it again:

http://code.google.com/p/noop/

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

I doubt that will be necessary.  Just wait until they figure out that almost* everything they are trying to do is already available in Scala, and then ship 'em the plugin you've already got.

--Dave

* I'm not a Scala expert yet, so that "almost" may turn out to be unnecessarily conservative.

0
Comment actions Permalink

According to this, the IDEA Scala plug-in is already a requirement for developing Noop in IDEA!


RRS

0
Comment actions Permalink

Given that the noop interpreter and code-generator is written -IN- scala, I'm not surprised at that

0

Please sign in to leave a comment.