Mathematica 9 is now available
Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
2007
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 2007

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

Search the Archive

Re: Best practice for Mathematica package development

  • To: mathgroup at smc.vnet.net
  • Subject: [mg77234] Re: [mg77149] Best practice for Mathematica package development
  • From: "Chris Chiasson" <chris at chiasson.name>
  • Date: Wed, 6 Jun 2007 06:47:50 -0400 (EDT)
  • References: <200706051029.GAA00593@smc.vnet.net>

1. make sure not to forget the back quote that precedes Private in
Begin@"`Private`"
2. become familiar with the Trace functionality (for investigating how
the masters do things)
3. ...

On 6/5/07, Andrew Moylan <andrew.j.moylan at gmail.com> wrote:
> What are the best standards and practices to follow when developing
> serious Mathematica packages that are intended for many people to use?
> Is there a handy guide, and/or template .m files, that can be used by
> prospective package developers?
>
> In the past I have made packages by allowing Mathematica to
> automatically generate .m files from a notebook containing the
> relevant definitions in initialization cells. With the advent of
> Workbench, I assume this is no longer the best method.
>
> I am interested in best practices related to managing options,
> contexts, warnings and errors, interfaces in general, etc. Is there a
> list of standards adhered to when WRI designs packages?
>
> Of course I can often see how others have designed packages by reading
> the .m files in their packages. Are all well-known packages as well-
> designed as each another? Can anyone recommend a particular package as
> a good example of how to write packages well?
>
>
>


-- 
http://chris.chiasson.name/


  • Prev by Date: Re: Version 6.0 Palettes
  • Next by Date: Re: unevaluated expression [CORRECTION]
  • Previous by thread: Best practice for Mathematica package development
  • Next by thread: Re: Best practice for Mathematica package development