Hi, thank you.
Apologies to everyone if was rude.
I am a C developer, and I love C, because is most powerful language
in my opinion. In my own code, I try do write the best C code possible,
following the masters K (The Bests).
So when I see the C being underused, I get frustrated.
Examples:
iupAttribGet(ih, "_IUPBUT_INSIDE_ACTION"), this is a lot inefficient,
when a simple static variable, solve and is very, very faster.
another is:
if iupStrEqualNoCase(value1, "ARIGHT")
In my own C code, never would use iupStrEqualNoCase.
There a 255 characters in char var, I prefer:
if (value1 == IUP_ARIGHT'), when value1 is simple char and
IUP_ARIGHT is 'A' constant.
This is simple examples, but IUP has a lots this.
I know this is my personal opinion, and IUP has historical reasons
to be like this. But I also know, that IUP has great potential to become,
Worlds first class, and run faster and secure, but by the way it's going to
take a long time...
Best regards,
Ranier Vilela
De: sur-behoffski
Enviado: sexta-feira, 7 de junho de 2019 01:59
Para: IUP discussion list.
Assunto: [Iup-users] IUP code priorities?! People care!!!
G'day Ranier,
Please do NOT get discouraged by the apparent lack of enthusiasm for
non-functionality improvements to the code.
I am 1000% on your side: Look back at all the warnings summaries I've
posted to the list over the years, and at one point, we got CD down to
merely 5 warnings.
In my opinion, Antonio has shown himself to be risk-averse in changing
the code, but there must be a strong drive to add new features, coming
from a direction that does not show itself on the list. As bugs in
these new features are found, they are fixed very promptly and always
in a way respectful of, and open to, the list.
Again, in my opinion, Antonio is doing a fantastic job given the place
he's working from.
There is quite a lot of third-party libraries incorporated in the code
base: In many cases, a current (at the time) stable version has been
configured for, and then copied in verbatim, into the codebase.
Sometimes this is because the libraries are not uniformly available
across all platforms, so this incorporation sidesteps that
potentially major maintenance nightmare.
A notable recent example of a library being optionally pulled back out
from the codebase is zlib: The codebase still has the version
snapshot from its time, but the build switches have been changed to
prefer using an external library where possible.
So, one way forward would be to continue taking incorporated
libraries and separating them back out, where possible.
You've probably seen my "warnings summary" output recently. I'll
post it again later today, to show how progress is being made.
[I regret not doing more sooner, but various factors have worked
against me... still, progress is being made.]
I'll try to post later today (Australian time), with an updated
warnings list. I'll also post the Lua script I use to parse the
GCC compiler output.
More later; in the meantime, your input has been fantastic, and I am
very grateful for what you've done.
cheers,
sur-behoffski (Brenton Hoff)
programmer, Grouse Software
___
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iup-users
___
Iup-users mailing list
Iup-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iup-users
