Mark H Weaver skribis:
> Shane Celis writes:
>
>> 6. Tag commands as special procedures perhaps by adding something to
>> their procedure properties. Implement a "command?" procedure. Export
>> commands and procedures to the same module. Then just pluck the
>> commands out of all the procedure
() Shane Celis
() Thu, 29 Aug 2013 16:57:00 -0400
6. Tag commands as special procedures [...] Implement "command?"
CON: Adding something to the procedure makes wrapping commands in
other lambdas awkward. Might necessitate a define-command,
lambda-command, method-command, which I'd p
Shane Celis writes:
> 6. Tag commands as special procedures perhaps by adding something to
> their procedure properties. Implement a "command?" procedure. Export
> commands and procedures to the same module. Then just pluck the
> commands out of all the procedures by using command?.
This is cl
Hello,
This is a really interesting question.
2 seems like the best combination of elegant and simple to me, but really
it's your preference. I wonder what other Guilers think.
Best,
Noah
On Thu, Aug 29, 2013 at 4:57 PM, Shane Celis wrote:
> Hello guilers,
>
> I'm developing Emacsy[1], and
Hello guilers,
I'm developing Emacsy[1], and I'm trying to design a good way of grouping and
exposing interactive commands. My interest is specifically related to Emacsy,
but for guilers in general the question is, How should one provide exports of a
different flavor? We have only "public" ex
