MathGroup Archive 2008

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: User defined options shared by more than one function - potential

  • To: mathgroup at smc.vnet.net
  • Subject: [mg90802] Re: User defined options shared by more than one function - potential
  • From: Jens-Peer Kuska <kuska at informatik.uni-leipzig.de>
  • Date: Thu, 24 Jul 2008 05:05:08 -0400 (EDT)
  • References: <g670of$s4u$1@smc.vnet.net>

Hi,

nobody put the Options[] into the public section.
You should only put usage messages in the public part.

Regards
   Jens

Donald DuBois wrote:
> Are there any compelling reasons for placing the
> statement
> 
> Options[functionName] -> {opt1->"", opt2->""}
> 
> in the public or private section of
> a user defined Mathematica package?
> 
> If there is more than one function that has the same
> option name then, to get rid of the option name
> showing up in red letters (because the option has been defined
> in multiple contexts when the functions are in different packages) then having the options defined in the private
> section of a package gets rid of this problem (i.e. the problem of having the option name, when used while calling a function,  show up in red letters).
>  
> Would it still be possible to have a usage statement for an option (to document its meaning) in the public section of a package, even though it is defined with the Option statement above in the private section?
> 
> Thank you.
> 
> Don
> 


  • Prev by Date: Re: Can't integrate sqrt(a+b*cos(t)+c*cos(2t))
  • Next by Date: Re: Can't integrate sqrt(a+b*cos(t)+c*cos(2t))
  • Previous by thread: User defined options shared by more than one function - potential
  • Next by thread: Re: User defined options shared by more than one function - potential