🚀 go-pugleaf

"Star" <noemai@noemail.com> wrote in message
news:46a65374$1@newsgroups.borland.com...

> If we use your approach, every time I find out my client stops
> working, I have to recompile my project after adding the right
> header and send the new version to our customers... Who wants
> to do that?

You would have to do that anyway.  If you enable all of the available
parsers (which you are doing now) and it still isn't able to handle a
particular server, then you'd have to recompile when you implement a new
parser that can handle that server.

> With Indy 9 everything worked great.

Not as great as you think.  Indy 9 couldn't handle most of the formats that
are actually used in the world.  That is why the new plugin system was
introduced into TIdFTP in Indy 10 to begin with.

> By the way, it seems that I'm not the only one who thinks that
> adding header files is not very intuitive. Even the developers say
> that in the documentation!

I have never seen the Indy documentation say anything like that.

> If I use IdFTP1->ListResult->Count I get the data correctly.
> The count is 2 and I get these 2 lines:
>
> drwxr-xr-x    2 0        0            4096 Jun 27 20:45 downloads
> drwxr-xr-x   22 0        0            4096 Jun 27 20:25 pub
>
> However, IdFTP1->DirectoryListing->Count is always 0.

Then you don't have a suitable parser registered correctly.  In this case,
that would be the TIdFTPLPUnix class in the IdFTPListParseUnix unit.  Which
would suggest that your project is not linking in that unit, since
TIdFTPLPUnix is registered when the unit is initialized.

> Don't you have Indy 10 on your computer?

Yes, but it is not in a usable state right now because I am doing a lot of
changes in it for the next release in the near future.

> Could you just test the code that I posted here?

No, I cannot.


Gambit