Leicaddict wrote:
>
> [email protected] (English Teacher) wrote in message news:<[email protected]>...
> > Should I learn C first? Or can I go straight to C++ or C#?
> >
> > Thanks in advance.
>
> C is dead. C++ is dying. C# is the future.
Dream on.
--
Karl Heinz Buchegger
[email protected]
Joe Thibodeau wrote:
> C is far from dead ... it is the backbone of just about every computing
> system out there. Every modern language has been influenced by C and as we
> speak C is the defacto standard for small embedded systems. Try cramming C#
> into a microcontroller domain space. Larger embedded systems use C++
> extensively. So the next time you pick up your shaver or get an ultrasound
> or turn on your car or listen to your stereo ... think C.
>
> My advice is to learn C first since it is the backbone for every modern
> programming language in the last 10 years.
>
> "Leicaddict" <[email protected]> wrote in message
> news:[email protected]...
>
>>[email protected] (English Teacher) wrote in message
>
> news:<[email protected]>...
>
>>>Should I learn C first? Or can I go straight to C++ or C#?
>>>
>>>Thanks in advance.
>>
>>C is dead. C++ is dying. C# is the future.
My Canon A2e replaced my old OM-1 system which was getting long in the
tooth. Now buying long lenses is not a waste of money.
Bob
On Mon, 27 Oct 2003 07:49:57 -0800, "Joe Thibodeau"
<[email protected]> wrote:
>C is far from dead ... it is the backbone of just about every computing
>system out there. Every modern language has been influenced by C and as we
>speak C is the defacto standard for small embedded systems. Try cramming C#
>into a microcontroller domain space. Larger embedded systems use C++
>extensively. So the next time you pick up your shaver or get an ultrasound
>or turn on your car or listen to your stereo ... think C.
Even C++ is C. It's just C with a *lot* or added routines...written
in C. Nor does C require all the DLLs of C++. Compiled C is so much
more compact than a stand alone C++ it's difficult to compare them.
Many refer to the visual languages as producing "bloat code"
You compile C, it gets even smaller (depending on how many libraries
you use). Compile C++ into a stand alone program and it becomes huge.
I compiled roughly 40 K of source for C++ and it became nearly 10
megs.
The most difficult part of C for almost any programmer is learning
pointers and dynamic memory allocation. That and depending on how
strong you have the type checking set it may let you do virtually
anything to anything with some rather strange and sometimes disastrous
results. But, it is important to learn how to use pointers, linked
lists, double linked lists and even circular linked lists. It's
probably easier to learn these concepts in either Pascal, or Delphi
which is far from dead as well...although it is suffering.
>
>My advice is to learn C first since it is the backbone for every modern
>programming language in the last 10 years.
Straight C is a relatively low level language, but far higher than
assembler. It's cryptic to read, but that same primitive level gives
it the power to do almost anything. Learn C and C++ will be a snap.
Just think of C++ as C with a lot of added routines already written
that give it the ability to work with object oriented apps. If you
already know C then you don't have to suffer with the basics while
trying to understand inheritances. <:-))
Actually VB is powerful and easy to learn, but not as powerful as C++.
Yet it will do most things an individual would want. OTOH it's
probably not going to be much help when looking for a job.
VB dot net is basically (no pun intended) VB with the dot net
capabilities added.
Yet, if a programmer is looking for a job the main ingredient is
having a degree, plus knowing the languages that particular firm uses.
With the current state of the industry, those doing the hiring can now
afford to be really picky.
You will find there are many obscure languages out there in use by
specific firms. Hence it's desirable to know "top down and bottom up"
*structured* programming. Be able to flow chart a program logically
(nasischneiderman? Never could spell it), and write pseudocode. Know
debugging inside out as you'll need it. Another important virtue is
knowing how to document your source code both internally and
externally in a manner than any one coming behind can understand.
Don't write documentation in such a manner that it takes an
experienced programmer to even get an idea as to what you are talking
about.
Roger Halstead (K8RI EN73 & ARRL Life Member)
www.rogerhalstead.com
N833R World's oldest Debonair? (S# CD-2)
>
>"Leicaddict" <[email protected]> wrote in message
>news:[email protected]...
>> [email protected] (English Teacher) wrote in message
>news:<[email protected]>...
>> > Should I learn C first? Or can I go straight to C++ or C#?
>> >
>> > Thanks in advance.
>>
>> C is dead. C++ is dying. C# is the future.
>
[email protected] (English Teacher) wrote in message news:<[email protected]>...
> Should I learn C first? Or can I go straight to C++ or C#?
>
> Thanks in advance.
C is dead. C++ is dying. C# is the future.
English Teacher <[email protected]> wrote in message
news:[email protected]...
> Should I learn C first? Or can I go straight to C++ or C#?
>
> Thanks in advance.
I'll get in before E. Robert Tisdale this time and point out that this is an
obvious troll. Please ignore it.
DW
"Thomas Matthews" <[email protected]> wrote in message
news:[email protected]...
> English Teacher wrote:
>
> > Should I learn C first? Or can I go straight to C++ or C#?
> >
> > Thanks in advance.
>
> This person should be reported to their ISP for network abuse.
> This issue has already been discussed in news:comp.lang.c,
> news:comp.lang.c++, news:rec.woodworking before. The
> clue is news:rec.woodworking.
>
> Please use your favorite search engine and search these
> newsgroups before posting.
>
> --
> Thomas Matthews
>
> C++ newsgroup welcome message:
> http://www.slack.net/~shiva/welcome.txt
> C++ Faq: http://www.parashift.com/c++-faq-lite
> C Faq: http://www.eskimo.com/~scs/c-faq/top.html
> alt.comp.lang.learn.c-c++ faq:
> http://www.raos.demon.uk/acllc-c++/faq.html
> Other sites:
> http://www.josuttis.com -- C++ STL Library book
>
not here
[email protected] (Leicaddict) threw a soggy newspaper
against the wall, and here's what stuck:
> [email protected] (English Teacher) wrote in message
> news:<[email protected]>...
>> Should I learn C first? Or can I go straight to C++ or C#?
>>
>> Thanks in advance.
>
> C is dead. C++ is dying. C# is the future.
At least put bait on the hook before you cast.
PMP
C is far from dead ... it is the backbone of just about every computing
system out there. Every modern language has been influenced by C and as we
speak C is the defacto standard for small embedded systems. Try cramming C#
into a microcontroller domain space. Larger embedded systems use C++
extensively. So the next time you pick up your shaver or get an ultrasound
or turn on your car or listen to your stereo ... think C.
My advice is to learn C first since it is the backbone for every modern
programming language in the last 10 years.
"Leicaddict" <[email protected]> wrote in message
news:[email protected]...
> [email protected] (English Teacher) wrote in message
news:<[email protected]>...
> > Should I learn C first? Or can I go straight to C++ or C#?
> >
> > Thanks in advance.
>
> C is dead. C++ is dying. C# is the future.
Pinhole lives!!! Hey where are those glass plates!
"Irrwahn Grausewitz" <[email protected]> wrote in message
news:[email protected]...
> [email protected] (Leicaddict) wrote:
>
> >[email protected] (English Teacher) wrote in message
news:<[email protected]>...
> >> Should I learn C first? Or can I go straight to C++ or C#?
> >>
> >> Thanks in advance.
> >
> >C is dead. C++ is dying. C# is the future.
>
> Leica is dead. Photography is dying. Camera obscura is the future.
> --
> Irrwahn
> ([email protected])
Speaking of trolls ...
"Kevin Goodsell" <[email protected]> wrote in message
news:[email protected]...
> Joe Thibodeau wrote:
>
> > C is far from dead ...
>
> Please don't top-post. If it's accepted on whatever group you are
> replying from then fine, but when cross-posting please adopt the Usenet
> standard formatting.
>
> -Kevin
> --
> My email address is valid, but changes periodically.
> To contact me please use the address from a recent posting.
>
Joe Thibodeau <[email protected]> scribbled the following
on comp.lang.c:
> Speaking of trolls ...
Are you out of your freaking mind?
*PLONK*
> "Kevin Goodsell" <[email protected]> wrote in message
> news:[email protected]...
>> Joe Thibodeau wrote:
>>
>> > C is far from dead ...
>>
>> Please don't top-post. If it's accepted on whatever group you are
>> replying from then fine, but when cross-posting please adopt the Usenet
>> standard formatting.
--
/-- Joona Palaste ([email protected]) ------------- Finland --------\
\-- http://www.helsinki.fi/~palaste --------------------- rules! --------/
"To err is human. To really louse things up takes a computer."
- Anon
Leicaddict wrote:
> [email protected] (English Teacher) wrote in message news:<[email protected]>...
>
>>Should I learn C first? Or can I go straight to C++ or C#?
>>
>>Thanks in advance.
>
>
> C is dead. C++ is dying. C# is the future.
This troll looks very similar to the original troll to which it is
replying. I'd say this is the OP trying again to start a flame war for
the purpose of flooding the groups where this is clearly not-topical.
Please ignore it.
-Kevin
--
My email address is valid, but changes periodically.
To contact me please use the address from a recent posting.
[email protected] (Leicaddict) wrote:
>[email protected] (English Teacher) wrote in message news:<[email protected]>...
>> Should I learn C first? Or can I go straight to C++ or C#?
>>
>> Thanks in advance.
>
>C is dead. C++ is dying. C# is the future.
Leica is dead. Photography is dying. Camera obscura is the future.
--
Irrwahn
([email protected])
Joe Thibodeau wrote:
> C is far from dead ...
Please don't top-post. If it's accepted on whatever group you are
replying from then fine, but when cross-posting please adopt the Usenet
standard formatting.
-Kevin
--
My email address is valid, but changes periodically.
To contact me please use the address from a recent posting.
[email protected] (English Teacher) writes:
> Should I learn C first? Or can I go straight to C++ or C#?
>
> Thanks in advance.
Why the hell is this message cross-posted to newsgroups on
woodworking and photography? Follow-ups fixed; please desist from
posting to newsgroups which are not relevant to your question.
If you wish to learn C, then learn it. If your sole desire is to
learn C++ or C#, then you are much better off learning C++ or C#
without going through C first. In particular, if you learn C
hoping that it will give you a boost in your understanding of
C++, you are probably mistaken: you will have to unlearn several
things from C that have been changed in C++. Moreover, there are
things which are considered proper and correct in C that are
considered poor style in C++, and vice-versa; and both viewpoints
are often correct given the context of the separate languages.
--
Micah J. Cowan
[email protected]
English Teacher wrote:
> Should I learn C first? Or can I go straight to C++ or C#?
>
> Thanks in advance.
This person should be reported to their ISP for network abuse.
This issue has already been discussed in news:comp.lang.c,
news:comp.lang.c++, news:rec.woodworking before. The
clue is news:rec.woodworking.
Please use your favorite search engine and search these
newsgroups before posting.
--
Thomas Matthews
C++ newsgroup welcome message:
http://www.slack.net/~shiva/welcome.txt
C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.learn.c-c++ faq:
http://www.raos.demon.uk/acllc-c++/faq.html
Other sites:
http://www.josuttis.com -- C++ STL Library book
Well, in school, we had to make an "A". A C++ or C+ just wouldn't get
it. Where you go to school son?
On Tue, 21 Oct 2003 16:31:18 GMT, Thomas Matthews
<[email protected]> wrote:
>English Teacher wrote:
>
>> Should I learn C first? Or can I go straight to C++ or C#?
>>
>> Thanks in advance.
>
>This person should be reported to their ISP for network abuse.
>This issue has already been discussed in news:comp.lang.c,
>news:comp.lang.c++, news:rec.woodworking before. The
>clue is news:rec.woodworking.
>
>Please use your favorite search engine and search these
>newsgroups before posting.