>>The point I tried to make is that a variable will do as well, and in my opinion even better, if it is a text/value that is used only in one place. The example Jim Nelson reflected upon is a clear example of a text that is used in one routine rather than in many. If that text would occur in many routines, then the developer should reconsider the modularity of his code, rather than the variables-versus-constants debate.
>
>You're not nit-picking over the choice of message example, are you. That's not the point; it just happened to be the first example to come to my head, rather than spend half an hour thinking up a "real-life" example.

Exaclty but this can go on and on since everyone is entitle to his opinion, The only thing I can say is that the #DEFINE values get replaced at build time that's why everytime u change a h file it will go and rebuild all the classes in the project when you build the app.