Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | > | Lars Gullik Bjønnes wrote:
| > | > | > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | > | > #ifdef NEW_CODE
| > | > | > #endif
| > | > | > or:
| > | > | > create new files for the newstuff and conditional compile so that
you
| > | > | > can get the new stuff and all others get the ols stuff.
| > | > | | I don't think that's a good way to do any development sorry.
| > | > I have done it with success several times.
| > | | Ah... now I understand why there's a ton of "#if 0" in the code!
| > | | | > I cannot fathom why you cannot do it as well.
| > | | Because that's a waste of time and I don't like #ifdef.
| > What time? If it takes any longer, it will be by an minuscule amount.
|
| So you say... If you try, maybe you would realize that you can save
| some time by modifying your way of working...
| Personally, I think your way is cumbersome, not useful and a waste of
| time. By doing it your way your forced to stay with the same design,
| you are just correcting lines of code instead of correcting a design.
You are not even listening.
| If you are afraid to not be able to use SVN features, you could also
| keep a copy of current version in your hard-disk. Same effect...
|
| > It is not like this ifdef will stay forever.
|
| It appears quite a few stayed forever.
#if 0? Quite a different reason how those popped up.
| > Only till you have implemented the enchant stuff and got it tested.
|
| I think you still don't understand the problem and I am tired of it. I
| am done with it.
Nice way of being stuck in your own mindset.
--
Lgb
