🚀 go-pugleaf

"Warwick" <warwickb1@extradotcodotnz> wrote in message
news:41eb3e6d@newsgroups.borland.com...

> I didn't really want the data in the Memo component, which I am
> using  for something else. But if I pass NewMessages->Strings as
> an argument instead the compiler thinks I am passing a single String
> rather than a TStrings object.

You are supposed to pass in the NewMessages object itself, not one of its
properties:

    IdNNTP1->GetNewNewsList(NewsGroups[0], dt, false, Distributions,
NewMessages);

> It is difficult to tell which argument is the one the compiler objects
> to from the error.

No, it is not.  It is very easy to figure out which paramater is wrong.
Simply look at IdNNTP.hpp to see how GetNewNewsList() is actually declared,
then compare it to the error message to see which parameter(s) do not match
the declaration.

> As you can see I mistakenly thought it was a difference between
> AnsiString and string. I thought perhaps because string is a typedef
> for basic_string in  BCB.

It is true that 'string' (lowercase 's') is such a typedef.  However,
'String' (uppercase 'S') is a typedef for AnsiString, and is provided for
compatibility with Delphi code.

> Ok, thanks. Again I was unsure which argument presented the
> problem, the pascal definition has all arguments passed by reference.

Don't look at the Pascal definitions.  Look at the C++ headers instead.
That is where the compiler is getting its information from.


Gambit