On 14 Feb, goo...@sdc.org wrote:
> testing
> testing
> obm100: I am reminded anew just how fragile the RAM filesystem is.
> Willard
--
Willard Goosey goo...@sdc.org
Socorro, New Mexico, USA
I search my heart and find Cimmeria, land of Darkness and the Night.
--Robert E. Howard
I typically stay out of these types of conversations, but do find it
rather interesting how different people can have totally different views
on the same topic.
John, if you want to add it as a joke, here is a suggestion:
1. Add a checkbox that say "Strip unwanted EOF marker"
2. If the
IMO reliability, usability and user-friendliness should trump theoretical
programming principles whenever the two conflict.
I suspect the Model T's wouldn't even exist as such if William G had rigidly
followed the book; AFAIK "good programming practices and principles" are
suggestions and
That is funny but it's also true.
1. "Features" that no one ever uses tend to have or acquire bugs
2. Code that does not exist cannot have a bug.
All these rules of thumb and principles we adopt as part of our "programmer
code" have truth and value to them in the right context.
But there are no
>the only reason a shim is needed is because some other program did something
>bad...
Which program is that for example, exactly?
If we were reading punched cards, would the keypunch be "bad"?
Or, in a modern context, which one is *bad*, Notepad or Wordpad? You suggest
that Notepad is bad
>
>
>
Not to fan the flames of this argument but having programmed mainframes,
minicomputers and PC's as a general rule when communications (transference)
of TEXT files occurs between systems then alteration of the contents is the
norm NOT the exception paticularly for the control characters of
Steve, just revisiting this as I catch up on e-mails. As Brian suggested,
it can do no harm to just put fresh batteries into your Model 100, make
sure the memory backup power switch on the bottom is on, and power up the
computer. Nothing should overheat, spontaneously go wrong, etc. You may
