Subject | Re: [Firebird-Architect] Recompiling Firebird as a .net assembly |
---|---|
Author | Fabricio Araujo |
Post date | 2005-03-01T17:23:04Z |
On Tue, 1 Mar 2005 16:31:13 +0200, marius popa wrote:
same - the .Net working certainly will make much difficult the
porting. Since it's rules are completely different on the part of
memory allocation - a hot issue on FB-Devel these times (see memory
pool thread) - geez you'ld have a lot of work.... ;-)
>The CLI C++ I were not aware. But my argument reamains the
>On Tue, 1 Mar 2005 08:14:24 -0400, Daniel Rail <daniel@...> wrote:
>>
>> Hello Fabricio,
>>
>> Tuesday, March 1, 2005, 2:27:44 AM, you wrote:
>>
>> > Hmmm... I think nobody would mind, but since .NET does not
>> > provide a C++ language (only C# which is much similar to Delphi
>> > in its workings, but with similar syntax to C++) is not really a port
>> > but almost a total rewrite...
>>
>> Visual C++ 2005 will introduce a new C++/CLI syntax for developing C++
>> applications for .Net.
>> (http://lab.msdn.microsoft.com/express/visualc/default.aspx)
>
>yes he knows that but the problem CLI C++ is like java , compiling
>code to the vm
>and objects are garbage collected - i takes a lot of work : is like
>porting firebird code to java
>
>http://www23.brinkster.com/noicys/cppcli.htm
same - the .Net working certainly will make much difficult the
porting. Since it's rules are completely different on the part of
memory allocation - a hot issue on FB-Devel these times (see memory
pool thread) - geez you'ld have a lot of work.... ;-)