Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] [OCAMOLE] problem with guid
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Nicolas Cannasse <warplayer@f...>
Subject: Re: [Caml-list] [OCAMOLE] problem with guid
> I found the following problem with the last ocamole-pre library:
> # #load "ocamole.cma";;
> # open Ocamole;;
> # guid_of_string;;
> - : string -> Ocamole.guid = <fun>
> Then, guid_of_string "something" crashes the runtime interpreter.
> I have the log of the system, if that can be of any help.

Thanks for the report.
OCamole haven't yet been tested under the toplevel.

> The function add_label should allow to create a new label object to
> the (list of shapes of some) slide. However, I do not manage to find
> what are the "orientation:guid" parameter possible values ?

Note that ocamole can't really answer to theses questions. You should try to
figure out how you would to that in VB and then translate into OCaml ( if
find somewhere the PowerPoint VBScript Help )

> guid_of_string and string_of_guid seem to be the only available
> functions to manipulate guid, but then I discovered that the
> string_of_guid crashes.

a GUID is an unique identifier ( something like this :
{DA936B63-AC8B-11D1-B6E5-00A0C90F2744} ) which can represent a COM class
or... something else... There is a also way to retreive the guid from an
name ( such as "Excel.Application" ) : "guid_of_progid"

> I tried to retrieve information on already created objects, but most
> of the call to functions with return types "guid" failed (some
> exception was thrown from the COM side, stating "Bad return type", or
> something similar). Other methods worked (that is, any that does not
> need or return a guid), by the way.
> I suspect that the olegen possibly created a wrong COM interface here.

Seems like it does not come from the the generated interface but from the
type checking of returned values.
I'll invistigate this point.

Nicolas Cannasse

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: