http://www.k-wave.org/forum/topic/organizing-code-in-packages Support for the k-Wave MATLAB toolbox en-US Tue, 12 May 2026 23:36:45 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/organizing-code-in-packages#post-4370 Fri, 14 Mar 2014 15:40:24 +0000 Bradley Treeby 4370@http://www.k-wave.org/forum/ <p>Hi DNF,</p> <p>It is a sensible suggestion, and would avoid the namespace issues. On the downside it would require us renaming all the function calls within the toolbox to include the package name (or adding an import call to the top of every function), and would break backwards compatibility with existing user scripts. I'll give it some thought going forwards.</p> <p>Brad. </p> http://www.k-wave.org/forum/topic/organizing-code-in-packages#post-4369 Fri, 14 Mar 2014 14:42:22 +0000 DNF 4369@http://www.k-wave.org/forum/ <p>Hi.</p> <p>Great toolbox! But, have you considered putting k-Wave in a Matlab package, that is, organizing it in a '+'-folder? One small annoyance while using k-Wave, and frankly most Matlab code, is namespace clashes.</p> <p>I have a number of functions called 'smooth.m' or 'gaussian.m' and so on, and need to care that one does not shadow another at various times. It would be very convenient if i could write</p> <p><code>&gt;&gt; mat_sm = kwave.smooth(kgrid, mat);</code></p> <p>or </p> <p><code>&gt;&gt; import kwave.*</code><br /> <code>&gt;&gt; mat_sm = smooth(kgrid, mat);</code></p> <p>I believe that using packages is something that Mathworks is trying to encourage, as well. </p>