> -----Original Message-----
> From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 15, 2005 5:37 PM
> To: dev@cocoon.apache.org
> Subject: [RT] How scripting made me hate java

>
> And I suspect a lot can be done by just documenting how
> existing cocoon
> committers do their development today, not *on-top-of* cocoon, but
> *within* cocoon.
>

A few days ago there was a thread titled "IntelliJ Open Source developer's
license". In this thread Ralph Goers, Sylvain Wallez,  and  Stavros Gounis
explained how they put their environments (resp. Intellij IDEA, Eclipse, and
NetBeans) into debugging mode  for various levels of Cocoon debugging. They
all three say it is easy in their environment. But when you read the
instructions, they appear far from trivial. This info should make it to the
Wiki. Especially because the topic of the thread does not cover this info.

Comparing debugging an interpreted scripting language versus debugging a
compiled language with "printf statements", I think being able to step
through the code and set breakpoints is a minimal requirement for the
compiled language.

Hugo Burm

Reply via email to