Re: [Rd] Segfault with options() (PR#7078)

From: <deepayan_at_stat.wisc.edu>
Date: Tue 13 Jul 2004 - 02:54:22 EST


On Monday 12 July 2004 11:37, Martin Maechler wrote:
> Thank you, Deepayan:
> >>>>> "Deepayan" == Deepayan Sarkar <deepayan@stat.wisc.edu>
> >>>>> on Mon, 12 Jul 2004 05:46:08 +0200 (CEST) writes:
>
> Deepayan> This is completely undocumented use of options,
> Deepayan> but it does cause a segfault with r-patched and
> Deepayan> r-devel on Linux:
>
> Deepayan> options(list('digits', 'scipen'))
>
> Deepayan> Strangely enough,
>
> Deepayan> options(list('digits'))
>
> Deepayan> and
>
> Deepayan> options(list(digits = 10, scipen = 2))
>
> Deepayan> work as might be expected.
>
> I think I've seen where and how the problem occurs and am
> currently testing an easy patch.
>
> That will however give an error message for all calls
> options( mylist )
> when mylist is a list that has
> length(names(mylist)) != length(mylist)
>
> You weren't making a "feature request" in the other direction
> where you?

No. I'm playing around with the possibility of having similarly behaved functions like lattice.options() and lattice.getOption(), and I was checking the behaviour of options() when I encountered the segfault.

Should options( mylist ) work at all? It's not documented, at least not in ?options. Is that a documentation oversight?

Deepayan



R-devel@stat.math.ethz.ch mailing list
https://www.stat.math.ethz.ch/mailman/listinfo/r-devel Received on Tue Jul 13 02:59:49 2004

This archive was generated by hypermail 2.1.8 : Wed 03 Nov 2004 - 22:45:02 EST