Is there a way to give a procedure access to it's argument list as a string?

I'm not convinced this is a good idea, because it would be quite disturbing to a reader of the code - it would be hard for the user to know that the code had this unusual side effect simply by seeing the code. Wouldn't it be better to make your function take arguments arg1 arg2 index2 and then inside you can access arg2[index]?

Anyway, if you really want to do this, you can use a macro - for example:

procedure(myProcReal(arg1 arg2 arg1Code arg2Code)
    printf("%L = %L\n" arg1Code arg1)
    printf("%L = %L\n" arg2Code arg2)
)

defmacro(myProc (arg1 arg2)
    `myProcReal(,arg1 ,arg2 ',arg1 ',arg2)
)

var1=vector(1 2 "abc" 3 4)
var2=vector("x" "y" "z")
myVar = myProc(var1 var2[1])

This outputs:

var1 = array@0x20e8038
var2[1] = "y"

Andrew

Yea - that code is beyond my skill level (a pun you're likely completely sick of by now). In order to not over burden you, I find myself framing my question in the simplest possible way but upon reading your answer feel I maybe should have not obfuscated my actual intent (which would have extended the scope of the initial question into something like "how do I go about architecting my code to do this?"). I need to ponder rewriting my code a bit before responding further. Many thanks as always for your rapid and precise answer.

I probably should have given a bit of explanation. Essentially a normal procedure has all of its arguments evaluated before it is called, so it can't see the literal arguments. There is a "nlambda" procedure, but use of that is discouraged (it doesn't play nicely with SKILL++). So the best approach is a macro - macros get evaluated early, and can see the code passed to the macro without evaluation. So all this macro does is convert the two arguments to directly pass through to an underlying function, plus quoting the code from each argument so that the underlying function sees the code too.

However, as I said, you probably don't want to do that ;-)

Andrew