- User Since
- Mar 27 2017, 4:48 PM (215 w, 2 d)
Feb 16 2016
"There are not many comments."
The code should comment itself, and /* some comment for block */ really need
only for description the strongly non-obvious actions - like complex math,
optimization (with answer why optimize here) or factorization algorithm O(1) :-).
Dear Neal, I thank you for answer.
This issue's the main goal is getting an answer to a question - Do you plan
support FLTK. I suppose that it may be closed with comment "not need this
toolkit" - so I do not format according to the GNU coding standards - There are
many contentious issues about the format code - 80 chars per line is more then
enough for assembler, but for C++ with templates - not sure.
Your code is your rules, so If you plan to accept FLTK support - I fix all notes.
email "firstname.lastname@example.org" is also my email, which I use in
github.com and because I use local git, it will be inserted automatically.
"the rest of the code has a fair number of violations"
For my studies and knowledge - can you post sample of violation?
Feb 12 2016
FL/fl_utf8.H in some distros is Fl/fl_utf8.h
input field tests removed
forget add resources
Patch adds fltk support to pinentry