Delete #ifdef DEBUG parts for release or not?

Question

When releasing source code for another user, when the coding style is not defined (pun intended) delete parts of #ifdefDEBUG?

(i.e. parts that are compiled only when defining DEBUG)

If I remove it, it will make the code look better (or should I look better - do I really want someone to know what I was debugging and how I did it?), But then I will lose the debugging parts or should contain two (or more) code versions.

What to do?

Answer 1

, "" , , . " ...", " ..." .

, , , , "" -. (, ...)

Answer 2

, . - , , , . ( )

: . , , , , - , ,

Answer 3

, . / , , , , DEBUG. , QA , , .

Answer 4

, script , .

Answer 5

.

, , , script, .

Do not support these secondary filtered repositories so that they are always generated.

But is it worth the time? Probably not, and you should probably just distribute everything, including parts of #ifdef DEBUG.

Answer 6

Maintaining multiple versions is NOTHING IMPOSSIBLE.

Just do it if you need to.