Then in the init.m file that launches the application all the Public files are read first and then afterwards all the Private files are read. Essentially you break each subpackage into two files - a Public file that declares the exported names and a dummy Private section, and a second Private file with no public exported names. There is a way to divide an application into subpackages that all have the same Context and that call routines from each other, criss-cross. But also you will have to include the second argument in the BeginPackage statement that declares subsidiary packages that are needed in a tree structure - as David Reiss advises. I don't feel like reproducing all of it right here. Mikel, If you will read my tutorial you will see how to name your packages and have access to them. Finance, Statistics & Business Analysis.Wolfram Knowledgebase Curated computable knowledge powering Wolfram|Alpha. Wolfram Universal Deployment System Instant deployment across cloud, desktop, mobile, and more.

Wolfram Data Framework Semantic framework for real-world data.

What can mathematica do