Hi team

Don't want to hijack a post here, so I created a new post.

@JohnInTX

What are some source code that I can read to improve my programming skills, thanks! Ideally start with some easy ones.

Thanks team!

 

I thought that Rosetta stuff was pretty good. The focus was on the method then the code.

The key for me when learning this stuff was to try to improve each time I did it. I rarely went back to improve existing, working code but often found better ways to do something the next time out. I also worked hard to learn the tools, assembler, compiler, macros etc. and use features of those to do build-time calculations, checks on stupidity etc.

I learned the basics from reading K&R, Plaugher, Knuth, Wienberg and other authors that addressed how to model solutions rather than just slam code together.

 

I’m going to talk to you about this via PM.

 

If you're looking for C code look here.

https://www.kernel.org/

Most of the driver code is easy if you understand C bit-banging and memory structures.
https://www.kernel.org/doc/html/latest/driver-api/index.html

 

Most of the driver code is easy if you understand C bit-banging and memory structures.
https://www.kernel.org/doc/html/latest/driver-api/index.html

Any reason why the kernel like to use this:

struct foo {
    int balh1;
    int blah2;
    ...
}

struct foo foo_1;

Instead of this:

typedef struct FOO{
    int blah1;
    int blah2;
    ...
}foot_t;

foo_t foo_1;

???

 

Any reason why the kernel like to use this:

struct foo {
    int balh1;
    int blah2;
    ...
}

struct foo foo_1;

Instead of this:

typedef struct FOO{
    int blah1;
    int blah2;
    ...
}foot_t;

foo_t foo_1;

???

Clarity of memory structures.
https://www.kernel.org/doc/html/v4.17/process/coding-style.html
5) Typedefs

 

Any reason why the kernel like to use this:

Answer: no.