🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.mac.oop.macapp3
Article #228

Re: Another one! (Part 1)

#228
From: Frank Becker Computertechnik,DE,...
Date: Wed, 06 Jan 1993 10:13
24 lines
1117 bytes
Dear MacAppers,
 
I think it is a good way to include every bug fix in a conditional compilation
so every one can choose if he/she will use the fixes or not.
What is about 3 of 4 defines like
 
o WellTestedFix
for changes that seem to work fine (this Fix was made three or more releases
before the actual version)
o TestedFix
for changes that seem to work fine (this Fix was made 2 releases before the
actual version)
o NewFix
as the Name show this are fixes which are new in this release, but checked from
someone.
o UncheckedFix
as the Name show this are fixes which are new in this release, but not checked.
 
I use actually only one define, but if we didn't get new releases I use more
defines for my own.
 
Best regards
 
 
Technical Details
Message-ID: <726316700.1475452@AppleLink.Apple.COM>
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!apple!applelink.apple.com

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!apple!applelink.apple.com
From: GER.XSE0201@AppleLink.Apple.COM (Frank Becker Computertechnik,DE,IDV)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Another one! (Part 1)
Message-ID: <726316700.1475452@AppleLink.Apple.COM>
Date: 6 Jan 93 10:13:00 GMT
Sender: daemon@Apple.COM
Organization: AppleLink Gateway
Lines: 24