Patrick Mc(avery schrieb:
>
>> Maybe it's a better idea, to use a search engine for "c++ for c
>> programmers". FLTK<- C++<- C, so it doesn't make sense, to jump from C
>> to FLTK, but learning C++ makes FLTK very easy.
>
> Perhaps I should have said "introducing FLTK's C++ subset to C
> programmers". If FLTK is using let's say half of C++, then could someone
> new to C++ start writing FLTK apps sooner by only sticking to the FLTK
> C++ subset? They could always learn the other have of C++ later, no?

To me programming C++ is really a difference (I know C from programming 
microcontrollers). I'm using STL classes a lot (that makes it easy and 
fault free to define data structures), I'm using streaming, because all 
can be a stream and streaming the same things to disk, memory, I/O, 
network and so on makes things also more easy. I prefer references to 
pointers, because this way they are always usable and also there are no 
memory leaks. (to mention this - I really would prefer FLTK to use 
string class, because it's the only place in my code, where char* is 
necessary). And I like to put all things to classes, because the 
software becomes modular and much more easy to understand and maintain. 
Also you start thinking in layers and objects, that's really different 
to languages like C, which tend to go into "Spaghetti Code".

There is a book from Bjarne Stroustrup "The C++ Programming Language" 
and reading this (a lot of years ago ;o) was the light bulb moment to 
me. So finally I want to say, if a C programmer is going to use C++, he 
should do the real thing and not some kind of "extended C", without 
understanding all the new concepts.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to