- Joined
- Apr 22, 2005
- Sythe Gold
- 23
- Messages
- 7,825
I hope you're joking.
Fun exam questions
- Thread starter Sythe
- Start date
I hope you're joking.
That is true. However, considering the whole world of programming, operating systems play a very small role. Unless you have to program specifically in C for some reason, if there are alternatives, people would not choose C.
Same thing applies for Assembly language. Even though it is still extremely crucial in hardware design and reverse engineering, it cannot be considered popular or worthy to learn.
- Joined
- Apr 22, 2005
- Sythe Gold
- 23
- Messages
- 7,825
Ever since Visual Studio .NET, the only way to write native Windows applications in Visual Studio is through C and C++. C is marginally faster than C++ (objects have an overhead), so unless you're using something like MFC, there is no reason to not use C.
I used to use the MFC AppWizard for my autos, but ever since discovering how much nicer plain-old Windows API is, I now use C instead.
I used to use the MFC AppWizard for my autos, but ever since discovering how much nicer plain-old Windows API is, I now use C instead.
Being plain and simple boosts speed of programs written in C. But in real world, run-time speed does not determine everything. Beside run-time speed, there is also speed of coding, speed of troubleshooting, speed of getting general support, speed of learning the language... Yea I am talking about it in a business perspective rather than strictly coding perspective. If you need to program for money or a living, C is not the best because most of the time, programming involving C requires much more time and effort for very simple tasks in general applications and time is money so you lose money here.
- Joined
- Apr 22, 2005
- Sythe Gold
- 23
- Messages
- 7,825
Ah, but, when dealing with the Windows API, the only difference between C and C++ code is one that has to do with the language itself, not the API:
The latter language can have variable declarations anywhere, whereas the former must have all variables declared at the beginning of the block indicating their scope. Everything to do with Windows programming; the message loop, the API functions, resources, etc. are just as easily accessible through either language.
Unless you're using or creating an object, is there really any reason to not use C over C++?
The latter language can have variable declarations anywhere, whereas the former must have all variables declared at the beginning of the block indicating their scope. Everything to do with Windows programming; the message loop, the API functions, resources, etc. are just as easily accessible through either language.
Unless you're using or creating an object, is there really any reason to not use C over C++?
I am afraid you are going off-topic here. I only wanted to point out not to waste too much time on C considering many other languages. Of course, one can learn C and have fun with it and even use it to make money if wanted to. I never said you must absolutely not learn or use it. When I said C became quite obsolete, I meant its popularity had gone down because of many reasons. If you can zoom out on your thinking, consider many other languages beside C, you can clearly see what I am trying to say. Just pointing out the fact in real world, not just my own opinion.
- Joined
- Apr 22, 2005
- Sythe Gold
- 23
- Messages
- 7,825
I also like C, remember Turbo C or Borland C in the old day. It was so fast and so simple.When I was forced to learn other languages simply because other people started to leave C, I was so disappointed.
What languages do you use these days?
- Joined
- Apr 21, 2005
- Sythe Gold
- 5,470
- Messages
- 8,074
- Discord Unique ID
- 742989175824842802
- Discord Username
- Sythe
http://langpop.com/
Most compilers, operating systems, applications and video games are still written in C/C++.
I would venture as far as to say if you don't know c++ you are unlikely to get a programming job in most cases.
did it all mentally while doing homework so it may be wrong. haven't used C in a while.
1) print hello world
2) infinitely
3) recurse infinitely
4) it creates infinitely many processes
5) cause a segmentation fault
6) char a[10]; int b = 5; a = 5;
? 7) void * (** foo)(void); yes
? 8) 9
? 9) compiler-dependent. depends on ambiguous operator precedence of postfix and prefix operators ++ and +
1) print hello world
2) infinitely
3) recurse infinitely
4) it creates infinitely many processes
5) cause a segmentation fault
6) char a[10]; int b = 5; a = 5;
? 7) void * (** foo)(void); yes
? 8) 9
? 9) compiler-dependent. depends on ambiguous operator precedence of postfix and prefix operators ++ and +
- Joined
- Jan 21, 2007
- Sythe Gold
- 0
- Messages
- 1,458
Q1: Yes
Q2: Infinitely.
Q3: Infinite loop
Q4: Fork bomb
Q5: The if statement is just a regular statement in disguise. After this, the code block prints out the value assigned to *'z' (8).
Q6: Sets the 5th index of a[] to 5.
Q7: It's a function pointer to another function pointer type.
Q8: 011 (9)
Q9: Either 2 or 3 depending on the compiler.
Q2: Infinitely.
Q3: Infinite loop
Q4: Fork bomb
Q5: The if statement is just a regular statement in disguise. After this, the code block prints out the value assigned to *'z' (8).
Q6: Sets the 5th index of a[] to 5.
Q7: It's a function pointer to another function pointer type.
Q8: 011 (9)
Q9: Either 2 or 3 depending on the compiler.
Similar threads
