From: Timothy J. H. <ti...@cs...> - 2005-02-14 21:55:50
|
On Feb 14, 2005, at 2:40 PM, Allegrini Christophe Bird Technology wrote: > =A0 > Timothy and JScheme users, > =A0 > Hello, > =A0 > Follow my previous email, I am ready to spend time to contribute to=20 > the evolution of JScheme. Great... > I think this project must live and evolve. JScheme will definitely continue. I will soon be adding one of my graduate students as another Developer and we'll work on writing up a description of the JScheme internals to=20= make it easier for people to understand the source code. > I have two little questions : > =A0=A0=A0 Does there exist a roadmap for JScheme? The current game plan for JScheme is * fix bugs as they arise * improve performance where possible (e.g. we are working on an=20 optimizing Scheme->Java compiler) * extend javadot so that it runs nicely under Java 1.5 on all = platforms * remain backward compatible * make it easier for people to use JScheme - more documentation - more sample code I would like JScheme to remain relatively small. One of the nice things=20= about Scheme is that it is a concise language. JScheme adheres to the philosophy of "small and=20= simple is good" by adding relatively few features (javadot, Threads, Exceptions, modules). I would be very interested in hearing what other JScheme users would=20 like to see in future versions of the language. We could be "BOLD" and create radically new versions of JScheme that=20 would not be backward compatible, but this would require us to maintain bug fixes on multiple branches of=20= the development tree. I'm not completely opposed to that, but I would prefer to keep JScheme simple=20 and just polish it so that it is a very nice, clean, powerful tool. > =A0=A0=A0 Are there documents describing internal architecture? Not yet, but this is part of the "more documentation" part of the game=20= plan. Cheers, ---Tim--- > =A0 > Best Regards, > =A0 > Christophe Allegrini > =A0 > www.birdtechnology.net |