This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: dotnet events and external language bridges
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Patrick Logan notes that Python.Net handles .NET events, while the current VW bridge does not:
For the record, the very nice production quality Python.NET does support dotnet events in the manner described above. I have not looked at the code for how, but it is open source.
There's a slight difference here that I should note - Python.Net is native to the CLR, while VW is not. We are supporting .NET in a bridging fashion - similar to the way we deal with making external C calls. One might ask why we are doing it that way, and there are reasons:
The CLR is not a friendly place for a dynamic language. Performance would be much slower for VW on the CLR
Any effort to run on the CLR would involve removing a fair number of our base libraries, and instead hooking to the .NET libraries. That would make it very hard to keep the cross platform value we have now
As I said in the earlier post on this, we intend to support .NET events; I'm just not willing to post a firm date for such support yet
Previous Topic
