Introduction and RFC
freds at jfrog.org
Fri Oct 26 04:34:56 PDT 2007
I really thought that the KSL was created exactly for that: Filtering
language proposals. But there are no mailing lists for KSL pure, and the Bug
database should not be populated with KSL noise.
About KSL, in my experience adding some code to javac (pure implementation)
to support small language proposal, is a lot faster and cheaper than:
- Evaluate the coherence/readability
- Evaluate its usefulness (in writing code and API)
- Evaluate its impact on current API
- Evaluate the risk impact on the javac and JVM
So, the KSL is great. Have it, play with it, throw it away (and "may be",
"sometimes", "rarely", "occasionally": keep it). And it does not have to be
Sun employees doing the steps. For me, once a language proposal and RFE
entry starts to get momentum (votes and so on), so the team leaders as
decided in the GB (Sun for the moment) can get involved and evaluate the
The KSL for me is "Extreme Agility", and luxury of having the
implementation before deciding if you need it or not.
So, please keep the spirit of it, it's good for everyone.
On 10/25/07, Dalibor Topic <robilad at kaffe.org> wrote:
> Ted Neward wrote:
> > Interesting--which list *would* be the proper place to discuss language
> > proposals? Is there one? (Personally, I thought it was this one.)
> I think the kitchen sink language project is the venue you are looking
> for: https://ksl.dev.java.net/
> dalibor topic
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the compiler-dev