From: Michael Y. <wo...@ra...> - 2008-03-22 15:20:57
|
* William S Fulton <ws...@fu...> [Fri, 21 Mar 2008 20:44:44 +0000]: > Michael Yurushkin wrote: > > Yes. It was rejecting of another (first) letter. And I wasn't > > registered. I beg your pardon. > > I have wrote you the short message about me - and I want to continue > our > > cooperation. > > I'd like to work with С# as a target. It's interesting for me - how > SWIG > > generates C# code from C++. First problems that occurent to me - are > > the problems with pointer-arithmetic..... > > Okay, describe the pointer arithmetic problem and send to the mailing > list please. > > William Good day. C# as we now, dosn't support direct working with pointers . Under "direct working with pointers" I mean such operations as +,-,>,< etc that are very often may be seen in the c++/C programs. To rich the aim of parsing such programs (from c++ to c#) there are some appproches. One of them - is using "unsafe" modifier - it's easy way but, it gives unverificated code. Another one - is more intersting - gives apportunity to get verificable code. Analyser will try to change int* (for instance) on dotNet classic array. And whole pointers (where it's possible) will changed by .net arrays. -- Michael Yurushkin. |
From: William S F. <ws...@fu...> - 2008-03-23 19:25:29
|
Michael Yurushkin wrote: > * William S Fulton <ws...@fu...> [Fri, 21 Mar 2008 20:44:44 > +0000]: > > Michael Yurushkin wrote: > >> Yes. It was rejecting of another (first) letter. And I wasn't > >> registered. I beg your pardon. > >> I have wrote you the short message about me - and I want to continue > > our > >> cooperation. > >> I'd like to work with С# as a target. It's interesting for me - how > > SWIG > >> generates C# code from C++. First problems that occurent to me - > are > >> the problems with pointer-arithmetic..... > > Okay, describe the pointer arithmetic problem and send to the mailing > > list please. > > > > William > > Good day. > C# as we now, dosn't support direct working with pointers . Under > "direct working with pointers" I mean such operations as +,-,>,< etc > that are very often may be seen in the c++/C programs. To rich the aim > of parsing such programs (from c++ to c#) there are some appproches. > One of them - is using "unsafe" modifier - it's easy way but, it gives > unverificated code. Another one - is more intersting - gives > apportunity to get verificable code. Analyser will try to change int* > (for instance) on dotNet classic array. And whole pointers (where it's > possible) will changed by .net arrays. > Okay. I think I need to see a use case to fully understand. By the looks of it you are thinking of a way to map C arrays directly onto C# arrays in a more natural fashion, which is something which is currently lacking. SWIG doesn't generate any code that uses the 'unsafe' keyword, but then it uses PInvoke, so everything nothing is safe as any pointer arithmetic in C/C++ is unsafe. So I don't see that making the code any less safe to be honest. William William |