From: Dmitry Bely <dbely@mail.ru>
To: caml-list@inria.fr
Subject: [Caml-list] bug report: camlidl
Date: 11 May 2001 13:32:22 +0400 [thread overview]
Message-ID: <pudg2puh.fsf@mail.ru> (raw)
Excuse me if I'm posting this to the wrong place -- I am new to the caml
community.
Here is the bug description. Let's consider the following example:
--- test.idl ---
[
object
]
interface IX: IUnknown
{
HRESULT something();
}
[
object,
pointer_default(ref)
]
interface IY: IUnknown
{
HRESULT_bool getBool();
HRESULT_bool getIX( [out] IX **p );
}
--- end of test.idl ---
$ camlidl -header test.idl
test.idl
$ ocamlc -ccopt /Zi -c -ccopt test.c
test.c
test.h(43) : error C2061: syntax error : identifier 'HRESULT_bool'
...
$ ocamlc -ccopt /Zi -c -ccopt /DHRESULT_bool=HRESULT test.c
test.c
test.c(76) : warning C4047: 'function' : 'long ' differs in levels of indirection from 'long *'
test.c(76) : warning C4024: 'camlidl_c2ml_Com_HRESULT_bool' : different types for formal and actual parameter 1
test.c(76) : warning C4020: 'camlidl_c2ml_Com_HRESULT_bool' : too many actual parameters
test.c(100) : warning C4047: 'function' : 'long ' differs in levels of indirection from 'long *'
test.c(100) : warning C4024: 'camlidl_c2ml_Com_HRESULT_bool' : different types for formal and actual parameter 1
test.c(100) : warning C4020: 'camlidl_c2ml_Com_HRESULT_bool' : too many actual parameters
test.c(126) : warning C4020: 'camlidl_ml2c_Com_HRESULT_bool' : too many actual parameters
test.c(147) : warning C4020: 'camlidl_ml2c_Com_HRESULT_bool' : too many actual parameters
So the following bugs are obvious:
1. HRESULT_bool (and HRESULT_int) definition is missed in camlidlruntime.h
(or camlidl compiler should always generate code with HRESULT instead of them)
2. The way compiler uses camlidl_c2ml_Com_HRESULT_bool() and
camlidl_ml2c_Com_HRESULT_bool() does not conform to their
definition. Specifically, the generated code implies some context structure
parameter while camlidl_*_Com_HRESULT_bool() definitions have no idea about
it.
Of course, I can easily fix the first problem myself, but in the later case
I have to give up -- ocaml internals are still beyond my comprehension.
If someone is capable to fix that, I'd be very obliged -- it's currently
the real showstopper for me :-(
Hope to hear from you soon,
Dmitry
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next reply other threads:[~2001-05-11 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 9:32 Dmitry Bely [this message]
2001-05-11 10:35 ` Dmitry Bely
2001-05-11 14:14 ` Alan Schmitt
2001-05-11 15:22 ` Dmitry Bely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pudg2puh.fsf@mail.ru \
--to=dbely@mail.ru \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox