I would like to see the ability to return multiple objects. Not sure if
this would be easy to do as it would require the preprocessor to work
across files, but I would like to do:
int i;
String str;
(i, str) = runCode();
public class Foo {
private property int i;
private property
Its not the generation I'm concerned about - I know there are tools to do
this. Its the fact that spitting out all this code becomes harder to
maintain. e.g. its very common for the javadoc comments on the member
variable, getter setter of a property to get stale or even meaningless.
Yah -
This is kinda off topic but I've been musing lately about a preprocessor
for
Java. One of the early attractions to me about Java some 5-6 years ago
coming from a mostly C++ background was that there was no pre processor
and
obfuscation, so Java code was very easy to read.
However in theses
Having followed this, er, debate with some amusement, I get the feeling
that if some of the energy directed at this list had instead been directed
towards JSR-47, then this discussion could have been avoided entirely. What
if JSR-47 had come up with a common interface that could be used outside
.
To: Jakarta Commons Developers List
Subject: Re: Workflow
Hi Colin
- Original Message -
From: *Colin Sharples [EMAIL PROTECTED]
BTW, I've been working on an implementation of the workflow system, which
definitely rocks. I've created an execution environment based on JMS -
activities
are in the context. Just feels a bit more natural.
Anyway, my colleague Preston Sheldon has created the two steps and updated CoreRuleSet accordingly - files attached.
CoreRuleSet.java NotAndStep.java NotOrStep.java
Colin Sharples
IBM Global Services New Zealand
CoreRuleSet.java
Description: Binary
