Re: Re: CodeProject, wxWindows, and wx.Net

If memory serves me right, Tom Malcolmson wrote:
> Yes, the managed C++ compiler is proprietary.  But, the output CAN be pure
> MSIL, and I believe that MSIL is part of the standard (ie. controlled by MS
> but otherwise public).   Therefor, I disagree with the statement 'Managed
> C++ does not run portably'.  To make sure that the output is pure MSIL you
> must avoid using unmanaged classes and API's (this is one of the reasons to
> use wx.NET instead of wxWindows).

... Ok, I got that point (ie use wx.NET with MC++) , but that confines it
to .NET only , because there is no way to use the same code from traditional
C++ stuff..

> Windows Forms is no different.  

I do agree that PInvoke is necessary for this , but there are portable 
ways of designing stuff (dotGNU's winforms run on IPaqs and OS X ...) .
MS has no such interest in making it run everywhere (other than on winCE
on iPaq)..

What I had in mind was that unless you write code for pure IL mode,
Managed C++ is unportable . And if you write with a .NET twist it 
becomes impossible to use it in a non-.NET situation.

Having said all about this ... I do know that dotGNU has plans for a 
Managed C++ compiler .. starting from their Managed C compiler.

> use wx.NET instead of wxWindows in their MC++ program is that Mono or dotGNU
> might ship wx.NET with their dotNet runtimes.

Mono seems to have adopted Gtk# as their primary UI ? (their tools and demos
are all in it) .

/me bugs Bryan for a wx.NET screenshot again ...

Gopal
-- 
The difference between insanity and genius is measured by success


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01