Re: FTP functions

[John W. Eaton]

On 24-Mar-2008, Xavier Delacour wrote:

| Other than being a lot more work, I don't see how this solution is
| really any different from what is in octave-forge. The package as is
| provides the full interface, and is given in about 250 lines (most of
| which passes through to ftplib.

The SWIG solution may be OK.  I have not tried using it.  Looking at
the sources, I don't don't see any doc strings defined for these
functions.  Am I missing something?  Is there a way to insert the
Texinfo doc strings for the DEFUN macros in the interface definition
file you use for generating the wrappers?  How thoroughly are
arguments checked, and how are those checks performed?

| The package
| also includes a few test cases.

How about using a smaller file for your test?  Also, why did you
choose the gcc-objc sources?  I guess I would rather not find that
someone used a download of the Octave sources as a test case for their
ftp software.  Even though I don't take the Octave download stats too
seriously, I do use them as a first approximation of how many people
are using Octave (at least as a way of comparing to previous releases).

| Though you may be right that having a libcurl/liboctave wrapper might
| be useful for other things, especially non-FTP protocols. And
| incurring a needless dependency is not desirable, of course.

Especially one that is not maintained and that might be less
functional than a dependency we already have.

jwe