From pgilbert@bank-banque-canada.ca  Tue Jun 23 15:53:07 1998
From: pgilbert@bank-banque-canada.ca (pgilbert@bank-banque-canada.ca)
Date: Tue, 23 Jun 1998 10:53:07 -0400
Subject: un-settable pars
Message-ID: <98Jun23.111627edt.13457@mailgate.bank-banque-canada.ca>


      >> Warning in par(args) : parameter "cin" can't be set
      >> Warning in par(args) : parameter "cra" can't be set
      >> Warning in par(args) : parameter "csi" can't be set
      >> Warning in par(args) : parameter "din" can't be set
    PD> This comes from constructions of the type
    PD>   opar<-par()
    PD>   work.work.work()
    PD>   par(opar)
    PD> This gives complaints from unsettable items. Splus quietly omits them,
    PD> so I suppose that we really should do the same.

One solution here might be to set some attribute on unsettable items,
effectively indicating that it is not to be set and no warning is necessary.

Paul Gilbert


	[This was bounced by majordomo because of the match
	  /^subject:\s*uns\w*b/i [[= "u*su*scribe" with possible typos]]
	 that's why I made "unsettable" to "un-settable".

	 MM, list maintainer]

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._


un-settable pars
pgilbert@bank-banque-canada.ca