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/
- References:
- Best practice for Mathematica package development
- From: Andrew Moylan <andrew.j.moylan@gmail.com>
- Best practice for Mathematica package development