I think there are more appropriate places to discuss this kind of thing, dwks.Originally Posted by dwks
Amazingly, I did this one manually in "The GIMP" as well. You should see what's still to come...well, I guess that'll be later.
I think there are more appropriate places to discuss this kind of thing, dwks.
Amazingly, I did this one manually in "The GIMP" as well. You should see what's still to come...well, I guess that'll be later.
Last edited by MK27; 05-27-2009 at 05:11 PM.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
Okay, I'll stop talking now.
Just one last note: GCC doesn't optimize as well on SPARC as it does on i386, but it still does the loop-access-to-pointer optimization. (I picked SPARC because I know it's tricky to optimize for.)
Anyway, talk to you later.
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
>> As you can see, the generated assembly code is virtually identical.
I'm actually suprised their so similar. Interesting.
>> ps. nice avatar ;P
Isn't there some unspoken rule against stealing non-animated animated avatars?
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
Is that the Perforce diff tool?
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
dwks tells us it is "kompare" which I will hazard a guess that it's a KDE app. Being addicted to fvwm2*, I may have trouble getting that to work because of all the excessive integration (dbus, etc.) Which might be just as well, my little mind should stay away from looking too hard at the asm side of things.
So I'm happy to get the bottom line here from the pros.
*I've actually starting making coffee with a config script.
Last edited by MK27; 05-27-2009 at 05:48 PM.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
As I said, it's kompare, which is indeed a really nice diff tool for KDE. (That's the KDE 3 version of it.) It's my favourite diff tool.Is that the Perforce diff tool?
You may be addicted to fvwm2*, but just wait until KDE 4's KDevelop becomes stable, and try it (and khexedit and kompare and kdiff3). You may have to reconsider your addiction.
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
