From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: tell@telltronics.org, guile-user@gnu.org
Subject: Re: 1.5.6: (bound? ) missing from optargs.scm
Date: 01 Apr 2002 00:06:35 +0200 [thread overview]
Message-ID: <87lmc8pf2s.fsf@zagadka.ping.de> (raw)
In-Reply-To: <E16rAgs-0001zA-00@giblet>
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> Curious, what would you do differently if redesigning?
>
> well, i would hide SCM_MAGIC_SNARFER and require output file to be
> specified, omitting guile-snarf writing to stdout in favor of it being
> able to manage zonking the output file should the cpp fail in some way
> (model after "gcc -o"). indeed, this is what i did before the work was
> clobbered by foolish consistency w/ the mal-published past.
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.
I also removed the deprecation mechanism in the stable branch because
it partly duplicates the mechanism that we have already.
> the macros and what not are fine, IMHO. i'm just grousing because i
> find it unpleasant to work w/ coding cowboys (yes mvo that's you)
> who break things gratuitously and leave the pieces for others to
> clean up, all the while wondering what the big deal is all about.
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.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-03-31 22:06 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 [this message]
2002-04-01 1:42 ` Thien-Thi Nguyen
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=87lmc8pf2s.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-user@gnu.org \
--cc=tell@telltronics.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).