From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: tell@telltronics.org, guile-user@gnu.org
Subject: Re: 1.5.6: (bound? ) missing from optargs.scm
Date: Sun, 31 Mar 2002 17:42:50 -0800 [thread overview]
Message-ID: <E16rqqQ-0007YI-00@giblet> (raw)
In-Reply-To: <87lmc8pf2s.fsf@zagadka.ping.de> (message from Marius Vollmer on 01 Apr 2002 00:06:35 +0200)
From: Marius Vollmer <mvo@zagadka.ping.de>
Date: 01 Apr 2002 00:06:35 +0200
It was not clobbered, please look more closely at what I did. You
keep your '-o' option, and the rest of us gets to have command line
compatibility with the snarfer from 1.4. This compatibility comes at
very little cost, if you want to call it a cost at all: the user is
not forced to switched to a better usage of guile-snarf, he is merely
allowed to.
what was clobbered was encapsulation of mechanism (internals) which
would allow us flexibility in the long run. the general principle i
feel appropriate here is that: when starting, start w/ exposing as
little as possible; future changes are then relegated to "addition"
which is easier to satisfy normal compatibility constraints, than
"removal" or "renaming".
i felt that this principle was applicable (we are at starting point)
because "snarfer from 1.4" was not supported; adding retroactive support
is ok if the design was good, but it wasn't, so this was not really
justifiable.
the cost (aside from listening to me spew on like this) in a decision to
expose internals is always latent, which is understandably difficult to
perceive. however, i'm sure you know the value of encapsulation because
of the `bound?' situation and am very glad to not think about that any
more and to watch you DTRT (i do this by watching tasks/TODO -- if you
claim some task i won't touch it).
Yeah, I was not being very polite by snatching the hacking of
guile-snarf away from you. Your first reply did not sound like you
wanted to continue, tho.
i had invested time to weigh the factors (as i learned them), explain my
reasoning, and do the work. why would i want to continue when the job
was done? more importantly, on the plate is doc snarfing -- are we
going to see the same behavioral patterns repeated? more generally, i'm
about to open the doors to give more people write privs -- can you set a
good example for these people?
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-04-01 1:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 6:30 1.5.6: (bound? ) missing from optargs.scm Steve Tell
2002-03-28 8:52 ` Thien-Thi Nguyen
2002-03-28 23:32 ` Thien-Thi Nguyen
2002-03-29 6:40 ` Steve Tell
2002-03-29 7:44 ` Thien-Thi Nguyen
2002-03-30 2:26 ` Steve Tell
2002-03-30 4:42 ` Thien-Thi Nguyen
2002-03-31 22:06 ` Marius Vollmer
2002-04-01 1:42 ` Thien-Thi Nguyen [this message]
2002-03-31 22:46 ` Marius Vollmer
2002-04-24 17:52 ` Marius Vollmer
2002-03-31 22:59 ` Marius Vollmer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16rqqQ-0007YI-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-user@gnu.org \
--cc=tell@telltronics.org \
--cc=ttn@glug.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 read-only IMAP folder(s) and NNTP newsgroup(s).