Yes. I have nothing against emacs (since I haven't used it), but you would never see a true vim user chumping out like this. Perhaps too much cross-platform work has finally driven poor Jeff around the bend. Next week he will be telling us he's sick of the modular separation of monitor and keyboard and how his new ipad seems neat but not so easy to use as one might hope...after that it will be stuff like "Giving instant tea a shot".
http://www.vitaminshoppe.com/store/e...ci_sku=WC-1024
Last edited by MK27; 05-23-2010 at 08:30 AM.
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
I gave codeblocks a shot too. In the face.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
Well I have worked with bakefile in the past and if you are working with wxWidgets its almost essential but CMake is in more active development. What is your major beef with CMake? You say it doesn't solve the "moronic syntax of Make" which makes little sense when I don't have to use a single make syntax to support three platforms...care to clarify your remarks? Don't get me wrong: if there is a better tool of the kind I will take a look at it but this is the least painful of the breed IMHO...
MK I would rather have my....stones pounded flat with a mallet than pay for an ipad...not my cup of tea Also as I have remarked offline, CodeBlocks is going to have to do a LOT more selling before I will abandon the (to my eyes) vastly simpler and ATM way more reliable path of CMake. Less pain that autotools but more of a "do what I f-ing tell you to" tool that most click-and-drool IDEs...I am mostly watching what it does WRT project management and I can already see a land-mine coming that will make me bail if I step on it and it blows up: When it is linking against generated libraries, it is hard-coding a specific path to the .so so not only must the .so be in a specific position, the executable and YOU need to be in one (not the same one) too or nothing can find anything. For the dynamically loaded plugins I am working on, this is a show-stopper. I need .SOs that I can load from anyplace that ldconfig can find, not only-from-jeffs-project...
Actually I am the one laughing at someone who claims to know Emacs and doesn't:
GNU Emacs Manual
I don't know what your problem is with me Mario but keep it offline and in your pants if you cannot contribute something useful. The GNU Emacs manual refers to them as Macros, not abbreviations.
I'm not Mario, nor am I entirely insane, as this section of the manual seems more like what you were describing to me.
Nope; I use and was referring to the macro recording capabilities of Emacs, not that.
I went back and rechecked; I referred to "macro recorder" several times but if even that was lost on the reader the experienced Emacs user would recognize a keyboard-bound macro-playback from an abbreviation expansion in the keystrokes...but whatever.
Also from the "giving everything a look" dept, I am looking at Zacs alternative to CMake, Premake. It does many of the same things but requires one to learn Lua which is one of those "I know I should learn it someday but until I have a genuine need..." languages. Still if an *extremely* minimal subset can be learned enough to do multitiered projects like this one then I will give it a shot; else it just moved into a work-pain zone I don't need right now. I mean I could take everything I have spent the past two days fooling with CodeBlocks to get working and have CMake doing it better with just a few lines of text. But we will see; I am always open to a better make system. Even tried my hand at writing my own once (for cross-compiling on platforms none of the other systems supported). It worked but was not flexible enough, then I moved on from that project to one where the minimal tools needed to make that work (did not even have real silicon to work with, just a prototypical emulator) so my make system from hell sits on the shelf. Oddly Zac should be gratified that I did pattern it after bakefile..just with more commands to support other platforms than the usual suspects..