MathGroup Archive 2008

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

Search the Archive

User defined options shared by more than one function - potential

  • To: mathgroup at smc.vnet.net
  • Subject: [mg90766] User defined options shared by more than one function - potential
  • From: Donald DuBois <donabc at comcast.net>
  • Date: Wed, 23 Jul 2008 05:59:00 -0400 (EDT)

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: How to call or run a NB file in another NB file?
  • Next by Date: Running programs from the command line in Mathematica
  • Previous by thread: Re: Re: How to call or run a NB file in another NB file?
  • Next by thread: Re: User defined options shared by more than one function - potential