From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [cygport] enabling a replacement for "objdump -d -l"
Date: Tue, 12 Mar 2024 18:49:46 +0100 [thread overview]
Message-ID: <87sf0v8hmt.fsf@Gerda.invalid> (raw)
In-Reply-To: <85c3141a-bed5-46e0-8106-5f7d88faee88@dronecode.org.uk> (Jon Turney via Cygwin-apps's message of "Tue, 12 Mar 2024 17:41:56 +0000")
Jon Turney via Cygwin-apps writes:
> But I'm not being oblique here. I really do want comments.
Well, adding comments or proper POD is about the same effort, so I'd
tend towards the latter.
> I'm not sure what's so astounding about the suggestion that a fifty
> line script should have some comments in it that you can't believe I
> mean that literally...
As the saying goes: Communication is possible, but improbable…
> Well, OK. This is less useful to people who actually want to use it,
> though, requiring them to know that
> "DWARF_PARSE=/usr/share/cygport/tools/dwarf-parse.pl" is the right
> incantation.
>
> Perhaps "DWARF_PARSE=1" could be a shorthand for that?
I don't see why not, it just requires one extra test.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2024-03-12 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 19:51 ASSI
2024-02-20 3:42 ` Marco Atzeri
2024-02-20 18:21 ` ASSI
2024-02-26 19:29 ` Jon Turney
2024-03-11 19:35 ` ASSI
2024-03-12 17:41 ` Jon Turney
2024-03-12 17:49 ` ASSI [this message]
2024-03-12 21:39 ` Brian Inglis
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=87sf0v8hmt.fsf@Gerda.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/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).