Re: [vos-d] Swig

2006-03-13 Thread George Birbilis
Plus the GNU guys have been building a C# compiler that compiles to native code and targets native libraries (instead of a .NET [or compatible] runtime). So one could use it instead of C++ I suppose on Unix   ---George Birbilis <[EMAIL PROTECTED]>Microsoft MVP J# 2004-2006http://

Re: [vos-d] Swig

2006-03-12 Thread Hugh Perkins
Yeah, Neil is 100% right.   FWIW, I'm using Scite as my editor, and lescript as my build tool.   Scite: http://www.scintilla.org/SciTE.html lescript: http://manageddreams.com/utils/lescriptmar9.zip   Lescript lets you use C# as though it is a scripting language, ie you can do:   C:\> lescript --nol

Re: [vos-d] Swig

2006-03-12 Thread Neil Mosafi
That it costs anything is a common misconception:   The Microsoft C# compiler comes for free with Windows. You can download the Visual Studio 2005 Express Editions for free for a year. You can download other integrated development enviroments for free (such as SharpDevelop) You can build C# in Mono

Re: [vos-d] Swig

2006-03-12 Thread sconzey
The problem is that as far as I know, C# isn't anywhere near as portable as python, nor is it anywhere near as open. There are many free python development applications, whereas to write C# requires £300 worth of software. My vote's cast for python.On 3/12/06, Hugh Perkins <[EMAIL PROTECTED]> wrote

Re: [vos-d] Swig

2006-03-11 Thread Hugh Perkins
Hmmm,   After playing around a little with C#, I have to agree with Neil: C# rocks.   Just to throw some salt in the wounds of the Python discussions, I cant help thinking that C# has all the advantages of both Python (run from source, easy to read) and C++ (strong typing, runs quickly).   Btw, OSM

Re: [vos-d] SWIG help?

2005-09-30 Thread Peter Amstutz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Uh... I don't think so. The only large-scale change I did (which was a while ago) was to introduce empty virtual destructors in all the pure abstract interface classes, so that gcc4 wouldn't complain. But I don't see how that would confuse SWIG..

Re: [vos-d] SWIG help?

2005-09-30 Thread Reed Hedges
Thanks Hugh, that helps a lot. I was confused because it seemed to happen all of a sudden without too many changes in VOS, and the problem affects almost all of the Python classes. One additional thing I noticed is that this doesn't affect the *Ptr classes, e.g. Vobject class has the raise in __

Re: [vos-d] SWIG help?

2005-09-29 Thread Hugh Perkins
Not all objects can be constructed, for example anything pure virtual Swig attempts to detect which objects can and cant be constructed.  Sometimes it gets it wrong One way in which it gets wrong are where you instantiate a method in a derived class that was pure virtual in the base class.  If the

Re: [vos-d] Swig

2005-09-02 Thread Hugh Perkins
> Anyway I can't possibly agree with Hugh's statement about C# being the same as VB!  It's much closer to C++/Java Well, partly it's to be controversial :-)  but I cant help thinking that C# is a genius marketing from Microsoft for Visual Basic.  VB has generally been an excellent language for bus

Re: [vos-d] Swig

2005-09-02 Thread Neil Mosafi
Yep, not had much practise with managed C++ as I'm lazy and C# is so much easier (!), but I guess managed C++ could be the way to go for integrating with VOS as it can fully utilise the C++ classes.   Still there'd be work required to make the API more ".net like"  On 9/2/05, Peter Amstutz <[EMAIL

Re: [vos-d] Swig

2005-09-02 Thread Peter Amstutz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 2 Sep 2005, Reed Hedges wrote: Am I correct that it's no problem to call C++ code or link against a C++ library from .net? Would the C++ library (libvos for example :) need to be compiled with CLR (".net extensions") enabled? Reed See

Re: [vos-d] Swig

2005-09-02 Thread Peter Amstutz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At work we have a large application that incorporates Managed and Unmanaged C++, C# and several COM objects. .Net/CLR does a pretty good job of tying it all together without too much fuss (except for the COM objects, which are ugly and we're tryin

Re: [vos-d] Swig

2005-09-02 Thread Neil Mosafi
Hi   Well finally something I feel qualified to comment on!   I'm not sure about C++ functions, but you can definitely call C functions which are exposed in DLLs using P/Invoke in .NET.  It's very simple - you just create a bunch of .NET functions which match the C function signatures, then you can

Re: [vos-d] Swig

2005-09-02 Thread Reed Hedges
On Thu, Sep 01, 2005 at 11:32:11PM +0200, Hugh Perkins wrote: > What Peter said. I think. It's been a while :-) > > Random aside: I've been playing with .Net at work; it's kindof cool, though > it's basically VB with a C++ syntactic sugar. I dunno why people claim that > C# means the end of VB,

Re: [vos-d] Swig

2005-09-01 Thread Hugh Perkins
What Peter said.  I think.  It's been a while :-) Random aside: I've been playing with .Net at work; it's kindof cool, though it's basically VB with a C++ syntactic sugar.  I dunno why people claim that C# means the end of VB, since C# basically *is* VB.  It's still pretty cool though :-) HughOn

Re: [vos-d] Swig

2005-09-01 Thread Peter Amstutz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Welcome back, Reed :-) I haven't touched it for a 2-3 months, but when Hugh Perkins and I were working on it we had wrapped most of the core API and were working on wrapping the Property metaobject. I think the most important thing that needs to