🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> "Frank Burleigh" <burleigh@indiana.edu> wrote in message
> news:45e073c0$1@newsgroups.borland.com...
> 
>> But I don't see how it's possible to build a
>> program since the generated HPPs declare this type:
>>
>> TIdIPv6Address = array [0..7] of word;
>>
>> A number of functions return TIdIPv6Address.
> 
> The only functions/methods that return TIdIPv6Address are the
> following:

>     BytesToIPv6()
>     IPv6ToIdIPv6Address()
>     TIdStack.HostToNetwork(TIdIPv6Address)
>     TIdStack.NetworkToHost(TIdIPv6Address)
>     TIdBuffer.ExtractToIPv6()

With this included:

#include <IdSMTP.hpp>

compilation of my code produces:

[C++ Error] Idglobal.hpp(426): E2091 Functions cannot return arrays or 
functions
[C++ Error] Idglobal.hpp(466): E2091 Functions cannot return arrays or 
functions
[C++ Error] Idstack.hpp(176): E2091 Functions cannot return arrays or 
functions
[C++ Error] Idstack.hpp(183): E2091 Functions cannot return arrays or 
functions
[C++ Error] Idbuffer.hpp(147): E2091 Functions cannot return arrays or 
functions

> The likelihood of most users actually using any of those is minimal.
> Besides, none of those are declared to actually use TIdIPv6Address
> specifically in C++ anyway.  Borland translates them to use Word
> pointers instead.

I understand.  But still, the functions and methods are declared in the 
HPP files, so C++ is upset.  Is there a missing pragma of some sort that 
would produce the conversion to word pointer?

> The only property that returns a TIdIPv6Address is the
> TIdIPAddress.IPv6 property, which is ifdef'ed out for C++, since
> arrays can't be used for properties.

That at least has not been a problem.

>> The C++ compiler isn't happy about this type
> 
> Please be more specific.

E2091. A function was defined to return an array or a function. Check to 
see if either the intended return was a pointer to an array or function 
(and perhaps the * is missing) or if the function definition contained a 
request for an incorrect datatype.

;-)

I could of course operate in the library code.  But that wouldn't be the 
right approach so it's better if I seek your suggestions.

> 
> Gambit


Thanks Remy.