Re: Implementation of convn

[John W. Eaton]

On 27-Mar-2008, David Bateman wrote:

| Do we want to prevent the user doing this? Or is the idea to prevent
| them doing it accidentally. Why not add a call like
| 
| sharedprivate (fullfile (octave_config_info ("localapioctfiledir"),
| "polynomial"))
| 
| to
| 
| usr/share/octave/3.0.0/m/polynomial/PKG_ADD
| 
| and
| 
| sharedprivate (fullfile (octave_config_info ("localapifcnfiledir"),
| "polynomial"))
| 
| to
| 
| usr/lib/octave/3.0.0/oct/x86_64-pc-linux-gnu/polynomial/PKG_ADD
| 
| and have the "sharedprivate" function register with the symbol table
| code that an additional legal path to the private directories.. This
| gives us the freedom to add dependent private directories anywhere and
| prevents the user accidentally obtaining access to the private functions..

Would it be possible use the sharedprivate function to gain access to
any private directory from any other?  That would sort of defeat the
purpose of private directories.  Or is its restricted in some way?
How?

jwe