Comments for Memory: from VCL via VCL for .NET to .NET

re: Memory: from VCL via VCL for .NET to .NET

2002-12-12T05:53:38-08:00

Besides, using...

{$IFDEF CLR}Borland.Win32.Windows,Borland.Win32.Messages,...{$ENDIF}{$IFDEF WIN32}  Windows,Messages,...{$ENDIF}{$IFDEF KYLIX}...{$ENDIF}

...strikes me as being less to type, easier on the eyes and caters for additional platforms...

Memory: from VCL via VCL for .NET to .NET

2002-12-11T11:15:40-08:00

I was just reading your article and the in the .net version of the program, you said that the system.windows.forms.button control did not have the tag property, and it is there. In fact, every windows controls, thus inheriting from system.windows.forms.control base class, gets the tag property also.Check this link at msnd: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwindowsformsbuttonmemberstopic.aspJonathan

Memory: from VCL via VCL for .NET to .NET

2002-12-10T08:40:46-08:00

Regarding: {$IFDEF CLR}Borland.Win32.{$ENDIF}Windows, {$IFDEF CLR}Borland.Win32.{$ENDIF}Messages, {$IFDEF CLR}Borland.Delphi.{$ENDIF}SysUtils, {$IFDEF CLR}Borland.Delphi.{$ENDIF}Classes, {$IFDEF CLR}Borland.Vcl.{$ENDIF}Graphics, {$IFDEF CLR}Borland.Vcl.{$ENDIF}Controls, {$IFDEF CLR}Borland.Vcl.{$ENDIF}Forms, {$IFDEF CLR}Borland.Vcl.{$ENDIF}Dialogs, {$IFDEF CLR}Borland.Vcl.{$ENDIF}StdCtrls;This will never work. Due to the way the compiler's scanner needed to be upgraded in order to handle "dotted" identifiers. The compiler treats the string "Borland.Win32.Windows" as a single identifier, and so you can't have a conditional directive within the identifier. Of course this may (no breath holding here) change by the final release, however you should not depend on it happening.Allen Bauer.IDE Architect.RAD Products Group.