From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Porting Watcom 11.0 to djgpp Date: 7 Jan 2000 18:52:01 GMT Organization: Aachen University of Technology (RWTH) Lines: 20 Message-ID: <855ckh$ptl$1@nets3.rz.RWTH-Aachen.DE> References: <853fat$5q4$1 AT bgtnsc03 DOT worldnet DOT att DOT net> <3875D12C DOT F6931CFF AT is DOT elta DOT co DOT il> <8559hr$49a$1 AT bgtnsc02 DOT worldnet DOT att DOT net> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 947271121 26549 137.226.32.75 (7 Jan 2000 18:52:01 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 7 Jan 2000 18:52:01 GMT User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586)) Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Charles Wood wrote: > This is *NOT* fun, nor exciting, nor even moderately interesting to do. Well, for as much as we know, you're always free to not do it, then :-^) > Porting does encompass any other the things that make me Like to be a > programmer. Porting is work. Not a nice or funny hacking exercise, but tedious and unrewarding, *hard* work, most of the time. In the case at hand, the heart of the problem is that the code you're working on is, by its very nature, strictly unportable. It relies on compiler features like the (nonstandard) 'interrupt' keywords. If that interrupt stuff is needed, that's a clear sign that this code is *very* close to the hardware and O/S, where all portability becomes an illusion --- even portability from one compiler to the other. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.