Erlang/OTP R10B-10 has been released
Tue Mar 21 15:27:20 CET 2006
Bengt Kleberg writes:
> > a) Use conditional compilation and sprinkle changes throughout
> > the code. Ugly because it uses the preprocessor and because
> > code gets twice as long in many seperate places. Nice because
> > it's fairly easy to convince yourself that you haven't broken
> > the system for X.
> in the past ('85-'90) i tried this when programming in c. unfortunatly
> it was only myself i convinced about not breaking X. the software i
> wrote was often broken for X.
I suppose I get what I deserve for writing "fairly easy to convince
yourself" when I should have written "you can easily prove", there's
every chance someone will run off on an irrelevant tangent.
The standard way to make sure you don't break code by adding
conditional compilation is to pass the original and changed source
through the preprocessor and show that the source is identical,
e.g. using 'diff'. Obviously (?), the new code needs the defines set up
for compiling for the old system.
More information about the erlang-questions