mailing-list for TeXmacs Users

["Sam Liddicott" <address@hidden>]

To follow on from yesterdays message:

I can't believe I just got this to work! (I typed it in a text editor 
and cut-n-paste to texmacs in one go).

<assign|tt|<xmacro|x|<get-arity|<eval-args|x>>>>

I have a use of eval-args that doesn't segfault!

However I think it is not a good way to get the number of arguments 
passed to a variable macro, if the arguments have a side-effect (like 
increasing a counter or setting global variables) then eval-args will 
cause the side effect.

This macro will also give the number of arguments. I hope there is a 
better way than this though

<assign|ll|<xmacro|x|<length|<map-args|identity|tuple|x>>>>



I tried this, but it also segfaults

<assign|ll|<xmacro|x|<length|x>>>

I also tried something like this but it seg-faults:

<assign|ll|<xmacro|x|<quasi|<length|<tuple|<unquote*|<arg|x>>>>>>>



Sam

On 07/04/11 22:12, Jan Lellmann wrote:
> Hello,
>
> the following code reproducibly produces segfaults when I move the 
> cursor to the "x" inside the macro.
>
> This is bad, since it is the only way to get the number of arguments 
> passed to a variable macro.
>
> ----
> <TeXmacs|1.0.7.3>
>
> <style|generic>
>
> <\body>
> <xmacro|x|<get-arity|<eval-args|x>>>
> </body>
>
> <\initial>
> <\collection>
> <associate|language|american>
> <associate|page-type|letter>
> <associate|preamble|true>
> </collection>
> </initial>
> ----
>
> Any ideas why?
>
> Jan


--
[FSF Associate Member #2325] 
<http://www.fsf.org/register_form?referrer=2325>

<http://www.openrightsgroup.org/>