Hi!

6-Июл-2004 18:51 [EMAIL PROTECTED] (tom ehlert) wrote to Bernd Blaauw
<[EMAIL PROTECTED]>:

te> it's simply that to much has changed; far beond the necesary amount.
te> example:
te>   config.b :
te>     removed all comments,

     ? There was and is a lot of comments!

te>   build.bat
te>    changed MSCL8 to MSC
te>    changed TC2 to TC

     Yes. Becuase TC3 is not "TC", but "TCPP" family.

te>    changed comments :- to ::

     This is because comments should be differ from commented statements.

     Tom, changed batches was (re)published in this group many times.
Difference of current batch files with previous is that command line in
compiler now noticeably reduced, duplicated code in tc/bc makefiles now
reused (through including common makefile), some issues with MSVC is fixed
(for example, NMAKE/Borland MAKE/WMAKE are very different and there was hard
to make makefiles, which are acceptable for all of them). Also:

______________O\_/_________________________________\_/O______________
- all MAKEFILEs now look similar.
- "production" target replaced by "all" to eliminate warning from NMAKE.
- DEVICE\MAKEFILE: device.lib now created directly in ..\lib directory
  without intermediate copy.
- added SYS\TURBOC.CFG and UTILS\TURBOC.CFG; most options for compilers
  moved from command line to consequent KERNEL\*.CFG.
- SYS\MAKEFILE, UTILS\MAKEFILE: reused implicit rules from MKFILES\GENERIC.MAK.
_____________________________________________________________________
              O/~\                                 /~\O

etc.

te>    etc.
te>   etc...
te> not only that it was MSCL8 for some reason (because it's the MSC V8
te> compiler), this also makes MANY changes without any useful purpose.

     There _are_ "useful purposes". Most of them I publish earlier, when
many times (re)publish batch files. For example, BC5 renamed to BC, because
this name used for all BC++ (3, 4, 5), not only for BC5, and thus mislead.

te> but when reviewing changes, I'd have to review ALL changes and see
te> if there any new bugs introduced, and thats simply impossible due to
te> the sheer amount.

     For example, I was send here many small patches for dsk.c. Where was
your reaction? Void. :( Some time ago diff for, say, config.c was small, but
changes are accumulated over time, whereas you was not interested in this
process earlier. Now you blame me in this?




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Reply via email to