|
From: | Rik |
Subject: | Re: odepkg private functions in core |
Date: | Wed, 21 Oct 2015 07:59:47 -0700 |
On 10/21/2015 04:27 AM,
address@hidden wrote:
Jack, This occasionally happens. I can think of three solutions immediately, but maybe someone else can think of something better. 1) Have the "pkg load" script for odepkg add the core ode/private directory to Octave's path. 2) Move the helper functions up from the private directory into the ode directory. Rename them to have '__' prefix and postfix which indicates that they are really for internal use even though they are visible to the programmer. See, for example, scripts/plot/util which has __plt_get_axis_arg__.m, __default_plot_options__.m, etc. 3) Have the "pkg install" script copy over the necessary files from ode/private into the odepkg's own private directory. Given that you can't install a package without having core Octave around, these will always be available for copying. --Rik
|
[Prev in Thread] | Current Thread | [Next in Thread] |