On Sep 5, 2009, at 4:37 AM, Eduardo Cavazos wrote:
I guess it comes down to, can a macro "eval" that 'f' so that it's a procedure which can then be passed to 'procedure-arity'?
Even if it is possible to do that, when you actually run that code (say a few days after it's been compiled), f might be bound to a different procedure (or even a nonprocedure!).
BTW, this discussion about procedure arity came up in the first week or so of starting this mailing list, so, anybody who's interested in this topic might want to get back to the archives to see what was discussed and what came of it.
Aziz,,,
