>The difference between VB and "native" languages, is that VB is a
script language with internal interpreter.
>The executable file that is generated by VB actually contain byte code
that is translated and executed on run time.
>That means that you can do such things inside your code.
>I do not know if it is possible, but on Delphi you could create
something similar, using the interfaces of the IDE...
>Another trick is to write it to a file and parse it when needed :)
>Other then that, you can evaluate data on run time like in VB, so
that's the same...
I actualy write it to an seperate form with an memo, but it would be
nicer if this is integrated in the ide.
Simplest way is to write this stuff to console when DEBUG is defined and
write an special format @ example
DEBUGMSG: Yourmessage, lazarus parses gdb output and when something with
DEBUGMSG: is found it is added to the
Console. When you select you with to do an final build, DEBUG isnt
defined and the stuff isnt written to console.
The debug output window itself cannot be filtered and shows too mutch
information to be good for this
Things i mean. and thigs like write debuginfos to file are bad. You must
remove this stuff for every final build and it
Is work to implement sutch features to the applications. It s no "must
have" feature for the die but it could be very usefull i think.
Christian
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
