Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am a computer science student. I studied C, then came to C++[an object oriented one] and now Java[More Object Oriented]. My question is whether 'C' language is of any importance these days? Did I study it for the sake of studying the languages in the order in which they were developed so as to understand languages step by step?
Is there things that can be done only with C? What is it's scope?
The main scopes are:
drivers
operating systems
systems where performance is critical
small embedded systems (thanks Joachim)
C is still heavily used in situations where otherwise one would drop down to assembler, since it's one of the few structured languages to let users code that close to the hardware.
And a lot of what claims to be C++ code is C code with an OOP wrapper.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
At my university, my CS1 teacher has advised us to not use for(int i = 0; [code]; i++), because declaring a variable in line with a for loop will not compile on C versions prior to C99. As a computer science major, is there any legitimate reason for this? As it was standardized nearly two decades ago, I would think any still supported / developed software would have no trouble implementing this.
From my browsing it appears that extremely low level hardware development such as the Linux kernel may use a C90-ish codebase but that seems to be a very fringe case.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am wondering what is the difference between drivers and libraries in the embedded C programming. Assuming that I am using uControllers that only have application code/firmware like PICs
With respect to deeply embedded systems (such as the PIC) the distinction is generally that a driver is tied to the hardware and is not portable between platforms, while a regular library should be portable and have no direct hardware dependencies. This is not a hard and fast rule, however it is the most consistent one that I have come across in embedded systems.
It is also common for vendors to call a collection of drivers a library so in a way you can think of drivers as just a special type of hardware dependent library, and a library as simply a collection of related code.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
If I want to create a game in C with SDL for example, is there a reason of why I should use a scripting language like Lua with it (since alot of commercial games uses a scripting language)? I have heard that scripting languages often are faster to write and easier to read, but what should they do? (graphics? ai? input? etc).
They should interact with the various "programming primitives" that the native code implements. That is, the native code should only do enough to allow the scripts to function within the game (although "function" can sometimes mean speed-wise).
If that sounds cyclical... it is. There's no complete way to define at the beginning of development what responsibilities the native code will have as the project progresses.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I was reading a ton of tutorials and wanted to get into GBA Homebrew
Now, should i use C or assembly? I already know a bit of C, but asm wouldnt be difficult to me, and i was interested in learning it anyways.
So, which one?
C is easier to develope, specially complex and long programs, and it will take you way less time than making it in assembly, plus you can write assembly in c. Assembly on the other hand can get you better performance if done correctly and it's more flexible.
So I would say go ahead with C
The general rule for the asm vs C no matter what platform (that has both choices) is to use C and only if you really have to use asm for performance or other reasons use asm...
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am converting code written in perl to C language but before proceeding I would like to know the performance difference between perl execution and c language execution.
It depends entirely on what you are doing. Raw performance of an interpreted language like Perl isn't as good as C, but if you are accessing files, pulling information out of a database, or other things which aren't purely part of the language itself you'll find the performance difference is negligible and the benefit of an interpreted language is much easier maintainability.