move private code to private subdirectory

[shabbychef]

Arguably none of the code here other than sedumi.m is needed by the end user. However, having a file with an innocuous name like ddot.m or vec.m in this directory means an end user can accidentally put a 'homonym' file somewhere in their path which causes a bug or gremlin. The solution would be to put all code other than sedumi.m and possibly the example problems in conversion into a subdirectory called private.

[mcg1969]

I like this idea. I would welcome a pull request. What does everyone else think?

Do you know what version of MATLAB introduced the “private/“ functionality?

[shabbychef]

It exists at least in r2007b (the version I am using).

[mcg1969]

Very good. There's only one reason I can think of for not doing this: this is not considered the effort official repository. The folks at Lehigh University might not want to make the same change back on their local copy. I am not sure that a change this big merits a full fork.

[shabbychef]

I suppose a user is free to unzip the archive in a directory called private, and move sedumi.m one directory up. I will test if that is sufficient.
BTW, are there any unit tests?

[mcg1969]

No unit tests. It would certainly be a good idea.
Another option is to modify install_sedumi.m to move everything into a private/ subdirectory if possible. I'd let it fail softly if, for instance, the directory was read-only.