On Sun, Dec 12, 2004 at 08:53:55PM -0500, Albert Cahalan wrote:
> That goto should almost never execute. When it does,
> the stamp is a poor candidate for tinting and ought
> to be fixed. (thus the warning I had added about the
> fall-back processing -- did that actually print???)
Not that I ever saw. Though I may not have been looking.
But, then, Tux Paint's pretty quite on the printf() front, so you'd
/think/ I'd notice it. :^)
<snip>
> 1. The usage of mixed tabs as spaces prevents me from
> using a block indent command. (^K-,) Either spaces
> or tabs would be fine, but not mixed.
I blame VIM! Damned thing!!! I used to use only emacs, but have
been finding VI varients load a LOT quicker, plus take the least effort
to get syntax highlighting going. Beyond that, though, it's actually quite
a pain in the butt to use.
Maybe we should throw the code through prettyprint or something?
> 2. The indentation of '}' breaks autoindent. My editor
> does not contain a whole figgin LISP interpreter and
> a LISP compiler and LISP libraries and a kitchen sink.
> BTW, this also causes the human to make many errors.
Can you explain this one? Do you mean the Emacs style of this:
if (blah)
..{
....stuff();
..}
If so, then yeah... it's a pain when PARTS of the code is indented
like that, and others are indented in the more standard way:
if (blah)
{
..stuff();
}
> Basically, I am unable to change the indent level.
> The coding features of my editor work great on just
> about any style except the one used by Tux Paint.
> I feel like I'm using notepad.exe, though I'm not.
Sorry.
> I think /usr/src/linux/Documentation/CodingStyle is sane,
> even though it isn't my favorite. You need this for it:
>
> (defun linux-c-mode ()
> "C mode with adjusted defaults for use with the Linux kernel."
> (interactive)
> (c-mode)
> (c-set-style "K&R")
> (setq tab-width 8)
> (setq indent-tabs-mode t)
> (setq c-basic-offset 8))
Before I delve back into an Emacs environment, I'll see how painful
a post-processing would be with prettyprint or something similar, just
to get some 'cleaner' looking code into CVS.
Also, way down at the end of the to-do-list in my brain is a note to
break tuxpaint.c up into sane pieces. It wasn't a big deal when the code
was only ~2000 lines long, but now that it's reaching 15,000 it's getting
a little insane. (I can still navigate the code with relative ease... it
just takes far longer to compile than it should.)
We both need newer PCs. :^) Where are the grants, these days, anyway!? ;^)
-bill!
[EMAIL PROTECTED] Have I been helpful?
http://newbreedsoftware.com/ http://svcs.affero.net/rm.php?r=billkendrick
_______________________________________________
Tuxpaint-dev mailing list
[EMAIL PROTECTED]
http://tux4kids.net/mailman/listinfo/tuxpaint-dev
