[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: My First Computer (was Computing Editorial)
"Marc 'BlackJack' Rintsch" <bj_666@gmx.net> wrote in message...
> > People should be introduced to the Ralf Browns interrupt guide before
> > doing ANY programming.
>
> Why? This has nothing to do with learning how to write good, structured,
> correct and efficient programs. There are many platforms out there and
> there will be many more in the future where those interrupt guide is
> pretty useless.
And this is the problem. Interrupts are not always about Operating systems,
but the machines they run on. Since I know IBM compatables will be order for
many years to come, the interrupts specific to the hardware, it saves
writing some piece which attaches itself to something called DirectX, which
is a punishment in itself. The sad news about Windoze users is that
Micro$-off are writing it in such a way, that you cannot do that. Sure hope
Linux isn't following suit.
> If you learn the basics of a high level language on any system, be it
> a C64, an Apple, a CP/M system, a *nix or Windows, it should be easier to
> write programs for any system out there.
True, but interrupts can be used in high level languages (not just
assembly), sure it doesn't relate to the C64, Apple & depending on which
CP/M your using, but it's up to users to document the capabilities of each
system which is there to help improve programs. Take the Amstrad for
example, it uses a fairly substancial Firmware list & documents are
available for it, describing what that does.
Alteratively, I could have used GSX for some of the things (under CP/M) &
that would have made everyone else happy that happens to use a different
system with GSX available for it. But by using stuff specific to the machine
also helps improve programs, sure it's not portable, however the code is
there for others to interpret it for their system.
But of course it's not the basis for writing a good program (there are many
other things one can do to write a good program), but on a system like the
IBM it's a good way to show that you want the next bloke with his 386 to run
a program on his machine, rather than consentrate on the chap who has the
2.xx Ghz processor.
Ross.