Hi Ian, Hi List
Indeed I should have referred to functions of a class as methods.
It looks to me that someone coming from ANSI C needs to learn classes
with inheritence and overloading. Actually the class stuff is not going
to be so hard as I have experience with some dynamic languages, so it
looks like overloading is the only topic that I will have some trouble with.
Do you guys think there are many people out there that know C but not a
dynamic language such as Ruby/PHP/Python? Even learning OO in Lua and
Javascript I bet a lot of people end up learning about classical
programming vs prototypical.
Maybe once I get up to speed I could write a tutorial, "FLTK for C
programmers", does that sound like a good idea?
Thanks again to everyone-Patrick
On 11-07-20 05:08 AM, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> FLTK is tiny(and fast) I am hoping that if I stick to the smallest
>> possible subset of C++ then I will be able to handle it's
>> native API and
>> if I want to "look under the hood" then the small code base
>> would make
>> this a reasonable thing to do.
>>
>> Could anyone please correct or add to the following:
>>
>> Some C++ features are already not used:
>> templates, exceptions, RTTI, namespaces
> Fltk uses a fairly simple subset of C++ internally, to aid portability.
> (You can, of course, use as much or as little C++ as you like in your
> own code using fltk...)
>
> Versions of fltk from the 1.x series (I suggest you use 1.3.0 for now)
> do not use namespaces (though note that fltk2 does, and fltk3 probably
> will...) templates, exceptions or RTTI.
>
> It's possible to write code that looks just like C in C++, of course,
> and that does tend to be the most portable subset...
>
>
>> We call functions from classes:
>> return(Fl::run())
> Not quite sure what you are stating/asking here, can you clarify?
> Being pedantic, I'd say that classes do not have "functions" they have
> "methods", though the distinction is not important here ("functions"
> would be just like C functions, not a member of any class, in general.
> You can write C-style functions in C++, and they behave much as you'd
> expect.)
>
>
>
>> I don't really know much about the standard library, friend
>> functions,
>> overloading and exceptions but should I care? If I understand the C++
>> subset that deals with the above code am I pretty much ready
>> good to go?
> You don't need to know about exceptions for fltk.
> Overloading is probably not too important though might come in handy
> down the line.
> You may need to learn about friend classes at some point, though
> probably not initially.
> You will need to learn about inheritance though as that's a key way of
> extending your own widgets derived from fltk widgets...
> For stdio you can just use the C functions, you don't need to deal with
> the C++ stream classes or etc.
> You do not need to know about STL, BOOST or... Etc... Though all are
> useful once you get up to speed!
>
>
> SELEX Galileo Ltd
> Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
> 3EL
> A company registered in England& Wales. Company no. 02426132
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
> _______________________________________________
> fltk mailing list
> [email protected]
> http://lists.easysw.com/mailman/listinfo/fltk
>
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk