Are there reasons for beginner programmers to learn C ?
-
Python's a good starting language, the syntax is simple and it's easy to read, plus it enforces code indentation practices.
I've seen a little bit of Python (in MIT's video series), but not used it so I didn't feel I could recommend it.
-
_Josh_ wrote:
Imagine a c++ programmer armed with a few smart pointer classes from boost and the stl and no understanding of the underlying issues each is designed to address.
Nevertheless, Stroustrup recommends learning high-level procedural C++ and then learning the low-level stuff, i.e., the exact opposite of what you say.
Kevin
-
Yes, C is very good at teaching you HOW computers work. Think of C as super-assembly. (And if you learn assembly language first, C is a walk in the park.) I run across too much C++ code that would be much more stable if more C-type constructs were used. On the other hand, I've also dealt with too much C++ code that is nothing but C with classes and misses out on some truly great features of C++. I've also observed that C programmers who start thinking about encapsulation end up with many of the basics of C++. I remember when I very first learned C++ and realized that the this pointer is what I'd already been doing in a lot of my code, though having it built in was quite nice. Final point and a narrow observation; I've worked with several people whose first language was C#. Not one of them understood memory management. I've also found that they had a hard time moving "down" toward C or even C# code that had to be very hardware aware.
Joe Woodbury wrote:
I've worked with several people whose first language was C#. Not one of them understood memory management.
I am one of those people, and actually my first language is VB.NET. IDisposable[^] seems quite hard to implement correctly and even if you implement it there seem to be times when you simply cannot call it. Sometimes even Microsoft recommends not calling it if it gets to difficult[^]. There's also a great article on it right here on CP on the difficulties with IDisposable: IDisposable: What Your Mother Never Told You About Resource Deallocation[^]. In our company not calling IDisposable on a Crystal Reports Object caused quite some frustration... It led to customers not being able to print any more reports after 50 or something. Anyway, today a coworker had a problem. He had a BindingSource in WinForms and bound it to a list variable. After that he created a new list and assigned it to the variable. In his mind the variable and the BindingSource still pointed to the same memory. Unfortunately things don't quite work like that... Of course I wouldn't know how you guys fix that sort of stuff in C or C++. Anyway, having some clue as to what you're doing considering memory management is pretty handy at times, even in a high level language like C# or VB. But I think that's the problem, as a .NET programmer you're led to believe you don't need to know this stuff.
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Are there reasons for beginner programmers to be taught C instead of C++? I'm not even thinking about Object Oriented programming, but simple declarative programming. I'm reading a lot of questions on CodeProject and on StackOverflow where people ask about issues with C language features that are so prone to errors and defect that it makes me cringe. A lot of those issues could be handled by simple C++ features (memory management (new/delete, smart pointers), strings, collections, references, ... ) I know there are lot of legacy code out there and it should still be maintained, but old code "ways" should not be the emphasis of the education. :confused:
Watched code never compiles.
It may produce a spiritual awaking. C was deliberately written to be unrestricted (to port the Unix O/S). It does what it's told to do, no questions asked. That means you have to pay attention to what you're doing. That is a good habit to learn. I'd even go so far as to suggest you dabble with the in-line assembler.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Well I didn't really suggest an order, just that knowledge of both is required to make the most of c++. If people want an easier language there are plenty out there.
:thumbsup:
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS My LinkedIn Profile
-
Not as a first language. Nor should an OOP-only language (VB, C#, etc.) be the first language. In my opinion BASIC and Pascal (and maybe Perl?) are still good first languages even though they won't apply very well to modern business. Professional developers still to be smacked with C.
PIEBALDconsult wrote:
Not as a first language
How about assembly?
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS My LinkedIn Profile
-
Language feature should make our lives easier to make portability as transparent as possible. Using standard C++ libraries (streams, collections, algorithms, memory management, ...) ), I can write portable code that runs on major OS without the need to think about it.
Watched code never compiles.
Maximilien wrote:
I can write portable code that runs on major OS without the need to think about it
Lucky you ;)
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS My LinkedIn Profile
-
Yes, C is very good at teaching you HOW computers work. Think of C as super-assembly. (And if you learn assembly language first, C is a walk in the park.) I run across too much C++ code that would be much more stable if more C-type constructs were used. On the other hand, I've also dealt with too much C++ code that is nothing but C with classes and misses out on some truly great features of C++. I've also observed that C programmers who start thinking about encapsulation end up with many of the basics of C++. I remember when I very first learned C++ and realized that the this pointer is what I'd already been doing in a lot of my code, though having it built in was quite nice. Final point and a narrow observation; I've worked with several people whose first language was C#. Not one of them understood memory management. I've also found that they had a hard time moving "down" toward C or even C# code that had to be very hardware aware.
:thumbsup: And most c and c++ programmers usually become better java and c# programmers than those who have only developed in those languages.
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS My LinkedIn Profile
-
A cringe-worthy proposition! I'm quite pleased by the way the StringBuilder class works so nicely with interop.
-
Not as a first language. Nor should an OOP-only language (VB, C#, etc.) be the first language. In my opinion BASIC and Pascal (and maybe Perl?) are still good first languages even though they won't apply very well to modern business. Professional developers still to be smacked with C.
I somewhat agree, but I would chose those languages only for lower level of education.If it's for college than I am for C all the way. What the heck, C should be in secondary schools as well.
-
Joe Woodbury wrote:
I've worked with several people whose first language was C#. Not one of them understood memory management.
I am one of those people, and actually my first language is VB.NET. IDisposable[^] seems quite hard to implement correctly and even if you implement it there seem to be times when you simply cannot call it. Sometimes even Microsoft recommends not calling it if it gets to difficult[^]. There's also a great article on it right here on CP on the difficulties with IDisposable: IDisposable: What Your Mother Never Told You About Resource Deallocation[^]. In our company not calling IDisposable on a Crystal Reports Object caused quite some frustration... It led to customers not being able to print any more reports after 50 or something. Anyway, today a coworker had a problem. He had a BindingSource in WinForms and bound it to a list variable. After that he created a new list and assigned it to the variable. In his mind the variable and the BindingSource still pointed to the same memory. Unfortunately things don't quite work like that... Of course I wouldn't know how you guys fix that sort of stuff in C or C++. Anyway, having some clue as to what you're doing considering memory management is pretty handy at times, even in a high level language like C# or VB. But I think that's the problem, as a .NET programmer you're led to believe you don't need to know this stuff.
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}I'm always flabbergasted when I ask basic questions about using an object that implements IDisposable to developers with many years of C# experience and they are completely clueless, let alone the caveats about implementing it correctly. It's even rarer for developers to know about the using statement. I often wonder how their apps don't leak database connections all over the place. I worked with one system that completely threw me for a loop. Every object was created in a using block in a factory method and returned to the caller. Each object was auto generated with a sql connection as a property which was opened in the constructor. Calling dispose closed the connection so it could be returned to the "business logic" layer. :sigh: :doh:
Curvature of the Mind now with 3D
-
C is very important and a great way to learn exactly how a computer works, which is a double edged sword but if you push on through and gain a good understanding of C all other languages are a piece of cake.
killabyte wrote:
C is very important and a great way to learn exactly how a computer works
That's debatable. I'm taking a class that brings you from NAND gates and D Flip Flops all the way up to the operating system (so far I've built a computer (CPU + RAM) from only NAND and DFFs and an assembler), and I don't see much relation to C. Admittedly it's a better model than a higher level language like C# or Java, but it's still pretty far abstracted.
-
I'm always flabbergasted when I ask basic questions about using an object that implements IDisposable to developers with many years of C# experience and they are completely clueless, let alone the caveats about implementing it correctly. It's even rarer for developers to know about the using statement. I often wonder how their apps don't leak database connections all over the place. I worked with one system that completely threw me for a loop. Every object was created in a using block in a factory method and returned to the caller. Each object was auto generated with a sql connection as a property which was opened in the constructor. Calling dispose closed the connection so it could be returned to the "business logic" layer. :sigh: :doh:
Curvature of the Mind now with 3D
What you are describing there has nothing to do with having C# as a first language... Actually it has nothing to do with programming! It sounds more like these people were baking an apple pie and somehow ended up in an office with a computer where someone mistook them for programmers.
Andy Brummer wrote:
Every object was created in a using block in a factory method and returned to the caller.
I can't imagine how that would've been... Employee: "There's a bug in Visual Studio that throws ObjectDisposedExceptions at random!" Boss: "We better turn off the 'Break when a common language runtime exception is thrown'-option then!" Third person: "Perhaps there really IS something wrong in your software?" Employee: "Hell no! I'm even using the 'using' keyword with some Objects that can, for no appearent reason, be used with it. Microsoft recommends it!" Boss: "Good job, now we should send Microsoft a report on that Visual Studio bug..." Third person: "By the way, I'm out of apples, anyone here has some?" Employee: "Sure, if I can have an ounce of flour." ... :laugh:
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Language feature should make our lives easier to make portability as transparent as possible. Using standard C++ libraries (streams, collections, algorithms, memory management, ...) ), I can write portable code that runs on major OS without the need to think about it.
Watched code never compiles.
Maximilien wrote:
I can write portable code that runs on major OS without the need to think about it.
If you're writing generic algorithms, of course. Writing a high performance server or something comparable and it's a different situation. The standard C++ libraries make up a miniscule fraction of the code base I'm working on (and some of that is still tricky, such as the differences in UNICODE. A few days ago, I had a small class where the entire class is different between Win32 and Linux. Another class has huge differences between Win32 and CE; I haven't even looked at what the Linux version will be like. :) )
-
PIEBALDconsult wrote:
Not as a first language
How about assembly?
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS My LinkedIn Profile
No, but I had that before I learned C.
-
I somewhat agree, but I would chose those languages only for lower level of education.If it's for college than I am for C all the way. What the heck, C should be in secondary schools as well.
Oshtri Deka wrote:
for lower level of education
Exactly.
Oshtri Deka wrote:
for college than I am for C all the way.
Yes, after they have the fundamentals and before they're released on the world.
-
No, but I had that before I learned C.
PIEBALDconsult wrote:
No, but I had that before I learned C
I guess you learned a thing or two that you still find useful ...
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS My LinkedIn Profile
-
killabyte wrote:
C is very important and a great way to learn exactly how a computer works
That's debatable. I'm taking a class that brings you from NAND gates and D Flip Flops all the way up to the operating system (so far I've built a computer (CPU + RAM) from only NAND and DFFs and an assembler), and I don't see much relation to C. Admittedly it's a better model than a higher level language like C# or Java, but it's still pretty far abstracted.
lewax00 wrote:
That's debatable. I'm taking a class that brings you from NAND gates and D Flip Flops all the way up to the operating system (so far I've built a computer (CPU + RAM) from only NAND and DFFs and an assembler),
I call that an FPGA course. I was more talking about Microcontroller "computers" from the ground up with C. using the chipset data sheet to write a HAL from register addresses etc etc etc.
-
lewax00 wrote:
That's debatable. I'm taking a class that brings you from NAND gates and D Flip Flops all the way up to the operating system (so far I've built a computer (CPU + RAM) from only NAND and DFFs and an assembler),
I call that an FPGA course. I was more talking about Microcontroller "computers" from the ground up with C. using the chipset data sheet to write a HAL from register addresses etc etc etc.
-
Are there reasons for beginner programmers to be taught C instead of C++? I'm not even thinking about Object Oriented programming, but simple declarative programming. I'm reading a lot of questions on CodeProject and on StackOverflow where people ask about issues with C language features that are so prone to errors and defect that it makes me cringe. A lot of those issues could be handled by simple C++ features (memory management (new/delete, smart pointers), strings, collections, references, ... ) I know there are lot of legacy code out there and it should still be maintained, but old code "ways" should not be the emphasis of the education. :confused:
Watched code never compiles.
Life is too short to code in C/C++. Go with C#.
Everything makes sense in someone's mind
