Re: Bad Code

Article View: comp.arch

Article #13088

#13088

From: forrest
Date: Thu, 26 Feb 1987 18:22

14 lines
1099 bytes

My opinion of this is that it shouldn't be thought of catering
to bad code but instead as an excellent way of finding bad code.

I work in a group that produces software for many environments.
The code is developed on Unix. Since I'm in charge of VMS software,
I have to port it to VMS. You'd be amazed at the number of bugs
that I've found due to the fact that VMS protect the first page
of memory.

(Note: this is not meant to be a Unix vs. VMS posting. Unix could
also protect the first page and still be Unix.)

Jon Forrest
ucbvax!mtxinu!blia!forrest

Technical Details

Message-ID: <1733@blia.BLI.COM>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!pyramid!voder!blia!forrest

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!pyramid!voder!blia!forrest
From: forrest@blia.UUCP
Newsgroups: comp.arch
Subject: Re: Bad Code
Message-ID: <1733@blia.BLI.COM>
Date: Thu, 26-Feb-87 13:22:25 EST
Article-I.D.: blia.1733
Posted: Thu Feb 26 13:22:25 1987
Date-Received: Sat, 28-Feb-87 06:19:23 EST
Organization: Britton Lee, Los Gatos, CA
Lines: 14
Keywords: vms
Summary: Protecting the 1st 512 bytes of memory is a good idea