"Rob Coker" <[EMAIL PROTECTED]> writes:

> Are the people doing the actual development of gnucash using an IDE
> of any kind or command line gcc + gdb?  If an IDE, which one is it?

Absolutely.  Emacs is completely Integrated into my Development
Environment :>

Seriously, I use emacs for all the code editing, I use M-. (the
jump-to-tag) function to jump around the source, and sometimes I use
emacs to run the build.  When you do that, you can jump directly to
the errors in the source files from the (highlighted) output of the
compiler.  (M-x compile to build, and "C-x `" to cycle through the
errors.

I probably should let emacs runt the build more often, but old habits
are hard to break, so more often than not, I still run the "make" in
an Eterm, and just find the file manually.  I'm starting to change
that, though, since recently I've been spending less time on new code,
and more time on chasing bugs.

<FWIW-YMMV> I can't imagine not using Emacs, but I completely (well
OK, perhaps not completely :>) understand those who don't like it.  In
any case, I'm really glad that I've never been in a position of having
to choose between the OS I wanted to run and running
Emacs. </FWIW-YMMV>

> I'd like to start helping (at least in the C part, it'll be a long
> time before I can do much in scheme) but am pretty spoiled to gui
> interfaces.

Scheme's pretty easy as long as you don't get tripped up by weird
assumptions that other languages tend to instill you with, and as long
as you can get over any parenphobia you might have[1].  At least
that's my impression from people I've taught it to.  If you decide
you're interested, I can send you some pointers, and I'm always happy
to answer questions.

[1] And the best cure for that is making sure you have a competent
source editor.  Not having one would make lispish language programming
inordinately more difficult, and would be categorically silly.

-- 
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930

--
Gnucash Developer's List 
To unsubscribe send empty email to: [EMAIL PROTECTED]

Reply via email to