MathGroup Archive 1999

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

Search the Archive

calling routine before Needs[]

  • To: mathgroup at
  • Subject: [mg17093] calling routine before Needs[]
  • From: Dan Truong <dtruong at>
  • Date: Sat, 17 Apr 1999 03:34:58 -0400
  • Organization: IRISA, FRANCE
  • Sender: owner-wri-mathgroup at

When a user calls a routine prior to the Needs[] or Get[] then
he automatically defines the routine.
However, when the package is loaded afterwards, since the routine
is already defined, the true routine from the package cannot be
used (you get a warning though).

When one writes a package, how can he guarantee that the routines of
the package will override previous definition?
I get nowhere with Clear[] or ClearAll[], Remove["Global`*RoutineName"]
to work but will generate a warning if the user didn't make any mistake.
Is there a standard/systematic method to tackle this problem?

Another point:
In my package I need global variables to hold informations
- Is it legal (it seems possible at least) to declare variables in the
package (ie package variables declared outside the routines of the
When a notebook is saved as a package (.m file) it seems everything is
removed but function declarations.
- Another solution is to have a routine to build global variables at
initialization. How can we tell a variable does not exist? Is there a
routine like ExistQ or DefinedQ[] ?

  • Prev by Date: Re: version 2.2.2 and Windows 98
  • Next by Date: Re: Heip! How to draw a graph with log x axis.
  • Previous by thread: Ordering differential equations
  • Next by thread: Re: calling routine before Needs[]