From: Daniel Jacobowitz <drow@false.org>
To: Brendan Doherty <brendand@gentrack.com>
Cc: gdb@sources.redhat.com
Subject: Re: Type identification within a user defined commands
Date: Wed, 20 Oct 2004 23:48:00 -0000 [thread overview]
Message-ID: <20041020222207.GB13185@nevyn.them.org> (raw)
In-Reply-To: <7D8E31C9DCC5204AB4AA23315B352F5B2F0DE6@exchange.talgentra.co.nz>
On Thu, Oct 21, 2004 at 10:35:56AM +1300, Brendan Doherty wrote:
> Is it possible to identify the type of a variable passed to a user
> defined command.
>
> I'm trying to create a prettier print that displays information about
> the various classes that we use.
> I want to use the type to access attributes specific to that class.
>
> What I am trying to do is considerable more complex than the example
> below, bug it demostrates what I want to do.
No, it isn't possible. You'd need a real scripting language for this;
a Perl implementation was posted, and someone has said they're working
on a Guile implementation.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-10-20 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 22:22 Brendan Doherty
2004-10-20 23:48 ` Daniel Jacobowitz [this message]
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=20041020222207.GB13185@nevyn.them.org \
--to=drow@false.org \
--cc=brendand@gentrack.com \
--cc=gdb@sources.redhat.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