From: Emanuel Berg <moasen@zoho.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: Gnus work
Date: Wed, 04 Oct 2017 23:07:09 +0200 [thread overview]
Message-ID: <86poa262rm.fsf@zoho.com> (raw)
In-Reply-To: <87mv56d9t7.fsf@ericabrahamsen.net>
Eric Abrahamsen wrote:
> I think the main problem is not so much that
> the defuns are long, but that they do too
> much, there's overlap, and there's lots of
> work-by-side-effect. A long defun wouldn't be
> so bad if you could scan it and feel
> confident that you knew what it was doing.
More or less. The form always has an impact on
the contents. I think what you describe is in
part a function of the habit of writing too
long functions.
> What I *do* think is a problem is that
> variables and functions are named
> inconsistently, and often confusingly.
> It just makes debugging that much harder.
> But on the other hand, renaming just for
> renaming's sake...
Indeed, small steps while at it.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-10-04 21:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 18:32 Eric Abrahamsen
2017-10-04 18:43 ` Emanuel Berg
2017-10-04 18:53 ` Eric Abrahamsen
2017-10-04 21:07 ` Emanuel Berg [this message]
2017-10-04 21:09 ` Tim Landscheidt
2017-10-04 21:56 ` Eric Abrahamsen
2017-10-05 5:19 ` Adam Sjøgren
2017-10-05 17:35 ` Eric Abrahamsen
2017-10-05 17:51 ` Adam Sjøgren
2017-10-05 20:10 ` Eric Abrahamsen
2017-10-05 16:37 ` Sivaram Neelakantan
2017-10-05 6:53 ` Julien Danjou
2017-10-05 13:31 ` Lars Ingebrigtsen
2017-10-05 18:12 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86poa262rm.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).