I second that.Dare wrote:Actually you're a smart cookie and I don't think luck will be a part of the equation - you'll just nail it!
Wish me luck...
C# is a much better language to learn from a syntactic point of view. C++ was a compromise (oo built on top of C), whilst C# was essentially designed by MS to fulfil the role which java fills.
It has very strong similarities to java.
C++ is not a good building block to C#/java, nor the other way around.
It seems to me that C++ is a good learning curve for C++.
Hope this helps
It has very strong similarities to java.
C++ is not a good building block to C#/java, nor the other way around.
It seems to me that C++ is a good learning curve for C++.
Hope this helps
Vincit qui primum gerit
"The Old Farts Wins" or "He Conquers Who First Grows Old"
"The Old Farts Wins" or "He Conquers Who First Grows Old"
It really depends on what kind of company you want to attract. If you aiming for corporate types, you'll want to learn whatever those corps are using (advertising for). It may be C, but probably it will be MS software particularly .NET (C# etc). On the other hand, some companies are not really corp (MS) driven, and are looking for the 'problem solver' type of person and they don't care what lang you are using, so long as it gets the job done. In this respect you can use your PB skills. So take aim at the type of company (and its development culture) and study accordingly.Xombie wrote:I need something else that will attract the attention of companies
-
Edwin Knoppert
- Addict

- Posts: 1073
- Joined: Fri Apr 25, 2003 11:13 pm
- Location: Netherlands
- Contact:
I said c# is very easy to learn because of the ide is helping you a lot.
If it comes to ordinary pointerstuff and the more lower level coding, forget c#.
Nowadays it's called managed code and all these aspects are nearly hidden or impossible to you.
If you for example expected to work with a neat byte pointer for fast manipulation, forget it.
It is handier to dive into the help and look at a substitute object to do this.
For that c# sucks greatly, at the other hand, i had not very much a need for it since i'm doing asp.net (c#) only.
It's a different kind of programming, i must say the learning curve is steep since you'll need knowledge (find) a lot of stuff in the help or on internet before you can do anything with it.
After a while (a year or so) you have gathered enough info to develop rapidly.
If you want low level and 'basic' c, use an lcc or similar.
If it comes to ordinary pointerstuff and the more lower level coding, forget c#.
Nowadays it's called managed code and all these aspects are nearly hidden or impossible to you.
If you for example expected to work with a neat byte pointer for fast manipulation, forget it.
It is handier to dive into the help and look at a substitute object to do this.
For that c# sucks greatly, at the other hand, i had not very much a need for it since i'm doing asp.net (c#) only.
It's a different kind of programming, i must say the learning curve is steep since you'll need knowledge (find) a lot of stuff in the help or on internet before you can do anything with it.
After a while (a year or so) you have gathered enough info to develop rapidly.
If you want low level and 'basic' c, use an lcc or similar.
-
Edwin Knoppert
- Addict

- Posts: 1073
- Joined: Fri Apr 25, 2003 11:13 pm
- Location: Netherlands
- Contact:
-
Edwin Knoppert
- Addict

- Posts: 1073
- Joined: Fri Apr 25, 2003 11:13 pm
- Location: Netherlands
- Contact:
Can someone PLEASE tell me how the idiot could think of unitialized variables and the need of terminating a sentence (;) ??
Really what a stupid design!!
99.99999999999999999999% of your code NEEDS the variable to be set to null or 0 anyway.
Any speed issues do no longer apply imo.
(Or make it possible to not initialize if you must)
The few occasions my line get's to long, please let me break it with an underscore.
What a nonsense..
I think that person was using crack at that time.
Really what a stupid design!!
99.99999999999999999999% of your code NEEDS the variable to be set to null or 0 anyway.
Any speed issues do no longer apply imo.
(Or make it possible to not initialize if you must)
The few occasions my line get's to long, please let me break it with an underscore.
What a nonsense..
I think that person was using crack at that time.
Thanks for all the encouragement.
So far I have to say that it's giving me a nice headache. On the one hand, I'm seeing where a lot of the PB stuff (especially 4.0) is coming from and knowing PB helps. On the other hand, it feels like C++ is just a lot of crap tacked on to C. And tacked on badly. Kind of like when you're editing a really old program without a lot of time. You should just rewrite it to make it better/more compatible but instead you have to just add on stuff that makes it work for now.
Granted, I haven't done much with it beyond reading (so far) but that's just the feeling I get from it. 5 billion different ways to create a pointer for everything. It's scary. Makes me realize how lucky I am that PB is so nice, easy and fast
Incidentally, I read "Code" by Charles Petzold over the weekend. That was a real interesting read. It gave a lot of background on why things are like they are with computers. Some parts were a little blehhh but mostly I enjoyed it.
So far I have to say that it's giving me a nice headache. On the one hand, I'm seeing where a lot of the PB stuff (especially 4.0) is coming from and knowing PB helps. On the other hand, it feels like C++ is just a lot of crap tacked on to C. And tacked on badly. Kind of like when you're editing a really old program without a lot of time. You should just rewrite it to make it better/more compatible but instead you have to just add on stuff that makes it work for now.
Granted, I haven't done much with it beyond reading (so far) but that's just the feeling I get from it. 5 billion different ways to create a pointer for everything. It's scary. Makes me realize how lucky I am that PB is so nice, easy and fast
Incidentally, I read "Code" by Charles Petzold over the weekend. That was a real interesting read. It gave a lot of background on why things are like they are with computers. Some parts were a little blehhh but mostly I enjoyed it.


