toggle quoted messageShow quoted text
PDP11, wow that goes back quite a while. We used one in the first
commercial product I was involved in designing from the ground up,
way back in 1975.
On 7/2/2018 10:46 PM, ajparent1/KB1GMX wrote:
I like your rules
My standard for a function or any subroutine is simple do one
I guess that matches your no swiss knives. I call them overloaded
I think the best example of that is the SD library as it drags in
FAT. Its huge
and if all you want to do is read or write blocks FAT is not
needed or even
a file system. Or you can just do tag and bag directory and teach
to use a simpler system to talk to a block device. That is only
Took me a while to tear the whole thing down to
and block_read(blockNum, Buffer) Where buffer is a 512 byte area,
blockNum is a 32bit int. The difference is more than 10K of code!
Global variables are ok if used for that only. Not be cause the
needed a variable to store and intermediate result.
The offense i've seen is long ints when the counter never exceeds
and floats when the value is going to be an integer. Its
people forget the iron they are programing is basically a 8 bit
C and for that fact C++ is a small language, the libraries are
get their shorts eaten. You don't need a full string library for
a little 8bitter.
C seems to be there when others have come and gone. Just about
others are easy (Ruby, Python, Java) if you know C.
A a long time PDP11 user (I have Unix V2.11 and Ultrix V6(BSD
ITs funny to thing the 11 is a near native C machine (very CISIC)
the origin point for C and typically 128K bytes was a big
It teaches one brevity, modularity, and with care clarity.
I still use Small-c on many micros because it is C (more K&R
than ansi but hey
it was the 70s and ANSI was over a decade later) and small. I
like it because
it allows me to get as close to the irn as I care to and yet hide
the iron when I