Re: [ros-dev] Yarotows trunk integration

[Adam Kachwalla]

The issue I see with that is that it will clog up debug logs, when attempting to solve certain problems. Since the hacks only really need to be sorted out (and can only be sorted out) during compile time, I am not sure there's much point polluting the debug log with all that. Simple #pragma message things are fine IMO. On Tue, 26 Oct 2010 18:29:20 +1100, Javier Agustìn Fernàndez Arroyo <elh...@gmail.com> wrote: and what about using DPRINT1("HACK:.......<<whatever>>); 2010/10/25 Olaf Siejka <cae...@gmail.com> For similar effect I am trying to map out and record every known hack or unimplemented functionality: http://www.reactos.org/wiki/Bug_Filters#Hacks W dniu 25 października 2010 23:15 użytkownik Ged Murphy <gedmur...@gmail.com> napisał: //TODO and //HACK, etc in code are easily lost and forgotten about. I think it's time reactos started to move towards a set of '#pragma message' defines instead of losing messages of hacked or unfinished code. Ged. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev -- Give a man a fish and he will eat for a day. Teach a man to fish and he will eat for a lifetime. Give a man religion and he will die praying for a fish.

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev