On 10 Sep, Mark Taylor wrote:
> Changing them makes life very difficult for people (like myself) who
> try to keep up with *important* changes. When the MP3 output has
> changed, it is usefull to track down why it has changed, and thus code
> changes (which do not represent bug fixes or addition
On 10-Sep-2000 Mark Taylor wrote:
> 1. COSMETIC CHANGES
Maybe one day/week we should just pass the whole thing through a C prettifier,
picking a defacto style (like GNU) and then work from that.
Of course that's after we have a perfect mp3 encoder...
:)
later
mike
--
MP3 ENCODER mailing list
On Sun, Sep 10, 2000 at 05:23:32PM -0600, Mark Taylor wrote:
>
> LAME compiles on all modern OS's, and under dozens of C compilers.
> This fact alone means that LAME is effectively complient C code. No
> additional "complience" work is needed or wanted. If you disagree, start a
> discussion in
>
> I'm not too fond of your new naming-scheme for defines to check if a include
> has already been included (__VERSION_H__ f.ex.)...
>
> Generally this scheme is only for internal compiler defines and system
> includes, and normal projects should not use pre- and postceding underscores
> in de
