From: "vinuth madinur" <vinlin@linuxmail.org>
Subject: Two level declaration using "vardef".
Date: Mon, 21 Jun 2004 00:07:04 +0800 [thread overview]
Message-ID: <20040620160704.2987623C03@ws5-3.us4.outblaze.com> (raw)
Hello everybody,
One small query (:-}
In a two level definition like:
def test(expr p)= __temp_call(p) enddef;
def __temp_call(expr p)(text t)=
........
enddef;
so as to allow definitions for macros like "draw".
Now, I want to have a macro similar to "draw" but also I want to have a suffix attached to the macro name.
so, I did something like:
vardef test@#(expr p)= __temp_call@#(p) enddef;
vardef __temp_call@#(expr p)(text t)=
........
enddef;
But this will obviously not work. But then I also have to define the macro with "vardef" inorder to have "@#" suffix.
Can someone please help me here?
Thanks.
Vinuth.M.Madinur.
--
______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org
This allows you to send and receive SMS through your mailbox.
Powered by Outblaze
next reply other threads:[~2004-06-20 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 16:07 vinuth madinur [this message]
2004-06-20 16:36 ` Patrick Gundlach
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=20040620160704.2987623C03@ws5-3.us4.outblaze.com \
--to=vinlin@linuxmail.org \
--cc=ntg-context@ntg.nl \
/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).