Re: quickie question on command object access

• To: Curt Eggemeyer <curt@eraserhead.jpl.nasa.gov>
• Subject: Re: quickie question on command object access
• From: Daniel Cerys <cerys@BBN.COM>
• Date: Wed, 16 Mar 94 21:25:29 EST
• Cc: clim@BBN.COM
• In-Reply-To: <199403162350.PAA03464@eraserhead.Jpl.Nasa.Gov>
• Organization: Bolt Beranek and Newman Inc.
• References: <199403162350.PAA03464@eraserhead.Jpl.Nasa.Gov>
• Sender: cerys@BBN.COM

[I'm assuming that, with CLIM2 implementations available for the majority
of Common Lisp implementations, unless someone states otherwise, CLIM
questions/comments refer to CLIM2.  (I realize this is probably pretty
irritating for MCL users).]

Curt Eggemeyer writes:
 > Is there a neat clim function for returning all of the command-objects for
 > a given application (even if it has multiple command-tables)?
 > 
 > If not, just how to you get a command object? I see no reference in the clim
 > manual on how you can retrieve a command object given the command name and its
 > command-table (how do you get that too?), even though the reverse is done with
 > clim:command-name!

A Command object is simply a list of a command name and some arguments
(i.e. (com-foo 1 2)).  Because of the inclusion of arguments, commands
objects are dynamic creatures that are created while running a CLIM
program.  The command name is something like com-foo (a symbol).

It makes sense to statically look at all of the commands (as command names)
in a command table, but I don't think it is true for command objects.

As you probably already know, MAP-OVER-COMMAND-TABLE-COMMANDS :Inherited t
will map over all of the command names in a command table.  

Dan

• quickie question on command object access
• From: Curt Eggemeyer <curt@eraserhead.jpl.nasa.gov>

• Prev: spreadsheets & clim
• Next: Re: spreadsheets & clim
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)