[lazarus] Win32 Installer/Lazarus

[Stefan Hille]

Hi!

On Sun, Jul 18, 1999 at 01:47:54PM -0700, Curtis White wrote:
> That is very true. That would be a very nice option to have. But I think we
> should allow the person developing with Lazarus the ability to decide if they
> want the extra code or not. If we wrap all calls to the Debug class in an ifdef
> DEBUG that is defined in the Debug class, then in Lazarus, we could
> provide a Project Options swich that would either define or undefine the DEBUG
> directive and would either compile in or not compile in the code. This
> allows complete flexibility and doesn't force the developer to have a bunch of
> Debug code in their program that they don't want. 

I agree that the extra code for the debug isn't nice but I really hate to
have many "ifdef's" in the code. From my point of view there are 2
solutions:

  1. Let's live with the extra code and put the ifdef's only in the
     debug-class. This would give some extra code, but the cost would only
     be an extra call with a direct return. When thinking of performance
     this approach should be OK.

  2. Use the macro feature of fpc and use something like "DEBUGOUT"
     instead of a direct call to the debug class.
     I don't know much about the macro facility in fpc but if it's as
     powerful as in C this shoul work. (Personally I don't like to see
     such features in fpc-code but who cares...)

bye,

   Stefan
-- 
---------------------------------------------------------
Stefan Hille          email: stoppok at osibisa.ms.sub.org 
48155 Muenster	      voice: 0251/664695