www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.bugs - colored debugging information output

reply Tiago Gasiba <tiago.gasiba gmail.com> writes:
Hi all,

  I would like to purpose/ask the following: In Linux, as you know, recent
versions of the OS have colored debugging output information. GCC itself
does not support coloring the debug information, but we can have it by
using a script such as the one here -
http://www.mindspring.com/~jamoyers/software/colorgcc/.
  Is it possible for this feature to be included in a future release of DMD,
i.e. to support debugging colors natively without a script? Otherwise, does
someone know about a script that can do the same job as the one mentioned
above? For myself this feature is highly desirable :)
  Thanks!

Best Regards,
Tiago Gasiba

-- 
Tiago Gasiba (MSc.) - http://www.gasiba.de
Everything should be made as simple as possible, but not simpler.
Oct 17 2005
parent reply Thomas Kuehne <thomas-dloop kuehne.cn> writes:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tiago Gasiba schrieb am 2005-10-17:
 Hi all,

   I would like to purpose/ask the following: In Linux, as you know, recent
 versions of the OS have colored debugging output information. GCC itself
 does not support coloring the debug information, but we can have it by
 using a script such as the one here -
 http://www.mindspring.com/~jamoyers/software/colorgcc/.

As far as I am aware that isn't coloured debugging output but coloured compiler messages.
   Is it possible for this feature to be included in a future release of DMD,
 i.e. to support debugging colors natively without a script? Otherwise, does
 someone know about a script that can do the same job as the one mentioned
 above? For myself this feature is highly desirable :)

Adapting the colorgcc script for GDC should be very straight forward. Doing the same for DMD would additionaly require some change to the lines following "while(<GCCOUT>)". Adding that feature natively to the D frontend would require some work in the "void *::error(const char *format, ...) " sections. Maybe you try your luck to patch colorgcc and maybe port it to D? (250 lines of clean and well documented Perl) Thomas -----BEGIN PGP SIGNATURE----- iD8DBQFDW6C93w+/yD4P9tIRAjYoAJ9wA9qOoG+/MMrWYOnLCA0Dc87+BQCgpKpb DOql8Gl8tWC0UulJgpGq1JM= =7qn6 -----END PGP SIGNATURE-----
Oct 23 2005
parent Tiago Gasiba <tiago.gasiba gmail.com> writes:
Thomas Kuehne hat geschrieben:

 
 Adapting the colorgcc script for GDC should be very straight forward.
 Doing the same for DMD would additionaly require some change to the
 lines following "while(<GCCOUT>)".

I haven't tried out GDC as yet, so I can not say anything about this... I'm only using DMD.
 Adding that feature natively to the D frontend would require some work in
 the "void *::error(const char *format, ...) " sections.

Yes... I suspect so. Adding a flag like --color would be very simple. I personaly would just simply output the standard escape sequences found in the Linux man pages to produce colorized output...
 Maybe you try your luck to patch colorgcc and maybe port it to D?
 (250 lines of clean and well documented Perl)

That is exactly my problem... I known nothing about Perl. I have tried my best to change the script (with alot of googling), but my expertise with Perl is null. If someone knows Perl well enough to do this in 10min, I would be very thankfull, otherwise it might take me several months to accomplish it. The most difficult problem I would be expecting is how to differentiate a warning message from an error. Does DMD output any keyword like "warning:" or "error:"? Thanks! Tiago -- Tiago Gasiba (MSc.) - http://www.gasiba.de Everything should be made as simple as possible, but not simpler.
Oct 24 2005