Re: Saving Packages
- To: mathgroup at smc.vnet.net
- Subject: [mg86875] Re: Saving Packages
- From: "alexxx.magni at gmail.com" <alexxx.magni at gmail.com>
- Date: Tue, 25 Mar 2008 01:14:06 -0500 (EST)
- References: <email@example.com> <firstname.lastname@example.org>
What use? Different ones, depending on the project. Basically my "libraries" (as I prefer to call them) contain everything from generic utilities valid for many projects, to project- specific function definitions, which are however too cumbersome to reside in the main notebook. It is simply the usual breaking down of big programs that I'm used to do since the days of plain old C programming. I thanks everybody who answered me, yet the curious fact is that I'm still ignorant about WHY packages exist at all - in a parallel world to the .nb world. And, more to the point, what would change for the outside user if Wolfram would provide a GetNB function, performing everything Get does - but for notebooks? wondering... alessandro Jerry ha scritto: > alexxx.magni at gmail.com wrote: > > Thanks for the answers, everybody. > > I googled this group in the past posts for info on package management, > > but didnt find so much info - I'll have to dig deeper. > > > > Your answers were of course right: setting the cells as init cells did > > the right thing. > > > > Yet I'd like to explain better what is my larger problem is: > > to break down a big project in pieces, it is correct then to save big > > chunks of code definitions as packages? > > I'm asking because I'd like to still keep on modifying those packages, > > as in a standard notebook. But opening the .m file brings up a > > different interface, which although it seems useful (drop down boxes > > with Functions and Sections - I'd like to have them in the notebook!) > > it's not so clear to me if I'm losing something present in the > > notebook interface. > > > > What I'm doing now, thanks to your answers, is to work in the .nb > > file, modify it as needed, select all cells and set them to init, and > > save as .m file. Correct? > > > > > Sir, I am very curious: what would you then do with the .m > file? > What use does it have?