From: roy@panix.com (Roy Smith)
Subject: Re: Need help writing file-visiting macro
Date: 25 Jul 2005 12:45:33 -0400 [thread overview]
Message-ID: <dc34vd$iq2$1@panix2.panix.com> (raw)
In-Reply-To: 7e7jfegat6.fsf@ada2.unipv.it
In article <7e7jfegat6.fsf@ada2.unipv.it>,
Thien-Thi Nguyen <ttn@glug.org> wrote:
>roy@panix.com (Roy Smith) writes:
>
>> I want it to construct the corresponding _Impl.c filename and
>> visit that file. Is that possible?
>
>it is possible if the correspondance is at least heuristical.
I'm not sure what you mean by "heuristical", but it certainly is
deterministic. For a given file name X.mdl, the corresponding
implementation file will be X_Impl.c.
next prev parent reply other threads:[~2005-07-25 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 13:58 Need help writing file-visiting macro Roy Smith
2005-07-25 15:33 ` Thien-Thi Nguyen
2005-07-25 16:45 ` Roy Smith [this message]
2005-07-25 17:44 ` drkm
2005-07-25 16:50 ` Sergei Organov
2005-07-25 17:52 ` rgb
2005-07-25 21:02 ` drkm
2005-07-26 22:49 ` rgb
2005-07-25 18:05 ` Kevin Rodgers
2005-07-25 21:38 ` Martin Slouf
2005-07-26 15:52 ` Kevin Rodgers
2005-07-26 18:24 ` Martin Slouf
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dc34vd$iq2$1@panix2.panix.com' \
--to=roy@panix.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).