Re: D2005 - A Hated Product!

From: Jim Cooper (jim_at_falafelsoft.com)
Date: 12/14/04 

Date: Tue, 14 Dec 2004 22:56:51 +0000

> Only if your code relies heavily on attributes would this be a problem.
> If you stick with standard Pascal/VCL code, you should be able to avoid
> attributes altogether I'd think.

So why would you have a .NET version of your code unless you were using
something specific to .NET? Attributes come up a lot in the FCL.

> That's your opinion. I disagree.

I don't believe it was a good move for Borland - it was a financial
waste of time that would have been better spent elsewhere. I think it's
a pretty widely held opinion too ;-)

> Seems kinda silly to add a language feature and then tie it in with
> just .NET.

Why? There is support for it in the .NET world, so why not? Attributes
are exactly the same. Generics will be implemented in .NET, and only
possibly be introduced in Win32.

> Are you saying you're /for/ having the Pascal language differ so widely
> between platforms

In this case, yes, why not? Why would you want exactly the same code in
Win32 and .NET? I'm not convinced that is even possible except for
trivial applications. It means no Windows API calls, no third-party
components (or even Borland supplied components that are only available
on one side or the other). Are there any useful apps written like that?
If there are, is there any point in compiling them as a Win32 exe and a
.NET assembly?

Cheers,
Jim Cooper

_______________________________________________

Jim Cooper jim@falafelsoft.com
Falafel Software http://www.falafelsoft.com
_______________________________________________

Relevant Pages

  • Re: Microsoft Published SDKs <-> .NET SDKs Map
    ... I'm not real sure what you are looking for, but here is a map of Win32 to ... > incredibly comfusing. ... I want to avoid using unmanaged code and, frankly, ...
    (microsoft.public.dotnet.general)
  • Re: The End of Codegear: Delphi plug-in for Visual Studio
    ... .NET, not Win32. ... The context is the discussion about how CodeGear can avoid ... always trailing Microsoft in .NET development. ...
    (borland.public.delphi.non-technical)
  • Re: Long term strategy of Turbo Explorer
    ... altogether. ... You don't for parts that FPC does not support. ... My point was that there's no problem with Win32 for Delphi. ...
    (borland.public.delphi.non-technical)
  • Msvcp80.dll dependency
    ... dependancy walker shows that my simple win32 ... program needs Msvcp80.dll. ... Is there a way to avoid this? ... Prev by Date: ...
    (microsoft.public.vc.language)