Re: isis debugging info

Daniel Dewey <dd_at_email.domain.hidden> I second this !
>   and also suggest that a list of isis variables be collected
> together for quick viewing/checking, maybe by category.
> Perhaps as a file in the distribution along with, or part of,
> a default isisrc?

You can write a wrapper around the _apropos function to achieve some
of the above:

   isis> ifuns = _apropos ("Global", ".", 1);  % intrinsic functions
   isis> sfuns = _apropos ("Global", ".", 2);  % slang functions
   isis> ivars = _apropos ("Global", ".", 4);  % intrinsic variables
   isis> svars = _apropos ("Global", ".", 8);  % slang variables

   isis> print (ivars);

If you want apropos to do something like:

   isis> apropos trace
   Functions matching trace in the Global namespace:
    backtrace_filter
    _trace_function

   Variables matching trace in the Global namespace:
    _slangtrace
    _traceback

then you can use the following in your .isisrc file:

define apropos (pat)
{
   variable funs = _apropos ("Global", pat, 1|2);
   variable vars = _apropos ("Global", pat, 4|8);
   if (length (funs) + length (vars) == 0)
     {
	vmessage ("No matches for %s", pat);
	return;
     }
   variable name;
   if (length (funs))
     {
	vmessage ("Functions matching %s in the Global namespace:", pat);
	foreach name (funs)
	  {
	     vmessage (" %s", name);
	  }
     }
   if (length (vars))
     {
	if (length (funs)) message ("");
	vmessage ("Variables matching %s in the Global namespace:", pat);
	foreach name (vars)
	  {
	     vmessage (" %s", name);
	  }
     }
}

Thanks,
--John
----
You received this message because you are
subscribed to the isis-users list.
To unsubscribe, send a message to
isis-users-request_at_email.domain.hiddenwith the first line of the message as:
unsubscribe