[[EMAIL PROTECTED] - Tue Jan 14 15:02:04 2003]: > In message <[EMAIL PROTECTED]> on Tue, 14 Jan > 2003 14:49:31 +0100 (MET), "Stephen Henson via RT" <[EMAIL PROTECTED]> > said: > > rt> I've analysed this further and the cause seems to be that it bcc > 5.5 > rt> complains about taking the address of a structure that doesn't > have a > rt> complete definition. > rt> > rt> For example the following wont compile: > rt> > rt> typedef struct FOO_st FOO; > rt> > rt> extern FOO bar; > rt> > rt> FOO *pbar; > rt> > rt> pbar = &bar; > rt> > rt> but it has no problems on other compilers. > > I believe this is a compiler bug, which should be reported back to > Borland (unless they have a newer version of bcc that works > correctly). >
Yes that's what I thought. Any ANSI C experts care to comment on whether that is legal or not? > rt> If you add EXPORT_VAR_AS_FN in the BCC-32 entry in Configure as in > the > rt> VC-WIN32 entry it seems to compile OK and passes all the tests. > rt> > rt> I'll check in this fix soon. > > Sounds reasonable. It does reduce the efficiency a little bit by adding one function call per ASN1_ITEM access but this is done under VC++ anyway. Steve. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
