Re: A83: Re: Bugs in Sos v1.5

To: Miles Raymond <assembly-83@lists.ticalc.org>
Subject: Re: A83: Re: Bugs in Sos v1.5
From: Linus Akesson <lairfight@softhome.net>
Date: Sat, 10 Oct 1998 14:07:11 +0100
Delivered-To: assembly-83-outgoing@towerguard.unix.edu.sollentuna.se
In-Reply-To: <005901bdf3d2$fef82940$9007fea9@eddie>
Reply-To: assembly-83@lists.ticalc.org

On 09-Oct-98, Miles Raymond wrote:
>-----Original Message-----
>From: Linus Akesson <lairfight@softhome.net>
>To: Miles Raymond <assembly-83@lists.ticalc.org>
>Date: Friday, October 09, 1998 3:03 PM
>Subject: Re: A83: Re: Bugs in Sos v1.5

>>
>*CLIP*
>>
>>PS. (not particularly a reply to this msg) That includes checking for split
>>screen mode, restoring all flags you change, checking for low memory
>>situations, checking and relying on user preferences like contrast level,
>>output mode etc., not using names that users may want to change, like prgmA
>>or something, (boy am I picking on Joe today.. =)) accepting that the user
>>may have entered one or more y= equations etc. etc.

>Why not just screw the "User Settings" and just make a ROM call to the RESET
>DEFAULTS?  It'd take a lot less RAM and would be faster.  Talk about
>optimizing code... =)  Besides, the user would get accustomed to it.

>-Miles Raymond

Well, NO because coders should service the users, not force them into
anything. Yes, we sure enough _can_ force users to anything by doing f.ex.
like you said, but that's not the point. Sure, small utilities to help
yourself like romdump programs, port monitors etc. can be made as simple as
possible, but games or programs that other people would want to use _must_
accept user preferences.

Still, you PC/Mac users wouldn't get my point however long I went on about
it. =)

Linus

References:

Re: A83: Re: Bugs in Sos v1.5

From: "Miles Raymond" <m_rayman@bigfoot.com>