[Mono-list] Re: JavaScript and Mono

Andrew Stopford Astopford@beta.dabs.com
Thu, 9 Jan 2003 16:28:19 -0000


I can update for JANET

			janet 				JScript
Parser         	done 					done
Execution 	      C# (done)				C# (done)
node interpreter  done					done?
Basic runtime  	(runtime errors on mono) 	done?
Helper libs    	done					done?
Vsa integration 	0% 					done?
CodeDom integr. 	0% 					done?
Test suite      	0% 					done?

Steve/Jeron can you double check and correct me if I am wrong.

Note that other than the change to Reflection.Emit Janet is being ported
from C# generation to IL. Therefore all items above can be considered
from this respect as 0%. 

Cheers

Andrew

-----Original Message-----
From: Paolo Molaro [mailto:lupus@ximian.com] 
Sent: 09 January 2003 15:57
To: Simon Waite
Cc: mono-list@ximian.com; steve@snewman.net; japj@xs4all.nl
Subject: Re: [Mono-list] Re: JavaScript and Mono

On 01/09/03 Simon Waite wrote:
> That sounds good, I've no problem with LGPL, but I think the final
desision
> rests with miguel(wrt mono) and ultimatly the previous owner (I'm
sorry I

Steve Newman is not the 'previous owner' :-)
He's the author and has final say on his code (by changing the license 
in the sources).

I'll note that the javascript support needs several components
and the components may use different licenses, as long as they can be
linked together. Ultimately the author of the component decides the
license. Of course having a single license would result in less
questions on the list, I guess:-)
As I understand it, currently the status of the projects is basically
(I'm using 'done' as in pretty good shape):

		janet 		JScript
Parser          done 		done
Execution 	C# (working?)	node interpreter (status?)
Basic runtime   done		done
Helper libs 	done?		done?
Vsa integration none? 		done?
CodeDom integr. none? 		none?
Test suite      none? 		?

Both are missing Reflection.Emit support.
Please, whoever knows better the status, change the table and post an
update.
Once it's known what is missing for the complete solution and what the
two
projects can reuse from each other the authors may have a better idea of
what component of the complete solution may need a license change.

lupus

-- 
-----------------------------------------------------------------
lupus@debian.org                                     debian/rules
lupus@ximian.com                             Monkeys do it better

_______________________________________________
Mono-list maillist  -  Mono-list@ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list