Re: A86: DOWN+LEFT patch
[Prev][Next][Index][Thread]
Re: A86: DOWN+LEFT patch
A standard would be good though, like a little chart (and make it simple
so that the novice users aren't confused - say something like if two
programs have the same letter in their compatability code, they won't
work together. i.e.:
A = IM 2 interrupt
B = custom interrupt
C = custom on
D = custom off
E = custom slink
F = [sqrt]KEY
G... the rest of the programs
come to think of it that's not too hard. I'll come up w/ a standard
later, maybe an easier to remember one. Using the above scheme, for
example, my DOWN+LEFT patch would have compatability code "ACE". If
another program had A, C, or E in its compatability code then they
wouldn't work together. Note that B, C, D, E are given even if that
memory area is used (my program uses C and E for code & storage)
Joshua Grams wrote:
>
> You don't need a standard. He's just saying it would be nice if you said in
> a readme file or something that your program uses _alton, (sqrt)KEY, IM2,
> _altlfont, or whatever. That way pepole would know what programs could
> possibly conflict with each other. I think that's a good idea, and it
> wouldn't really take much work on the part of people writing programs, just
> one more thing to add to the readme file.
>
> At 03:37 PM 6/8/98 -0600, you wrote:
> >
> >sounds good. someone want to propose a standard?
> >
> >Stephen Hicks wrote:
> >>
> >> This gives me an idea. It might be helpful to include any hooks that any
> >> program uses in its documentation so ppl will know what they can't use
> >> together. Maybe some sort of little ascii chart would do the job?
--
=====================================
= =
= Kirk Meyer (mailto:_@ibm.net) =
= http://www.bigfoot.com/~kirkmeyer =
= =
= "Set your affection on things =
= above, not on things on the =
= earth." Colossians 3:2 =
= =
=====================================
Follow-Ups:
References: