Browse thread
Native executable symtable
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2004-11-11 (18:46) |
From: | Alex Baretta <alex@b...> |
Subject: | Re: [Caml-list] Native executable symtable |
[I'm sorry for the duplicate: I pressed the <Send> button by mistake.] Xavier Leroy wrote: The insight about modules implementing abstract data types differently is very interesting. I had not thought about this. So, yes, what we really want is a *hard* checksum, taking into account the implementation, too. > let _ = Registry.record_module "Modulename" "checksum" We have considered the Checksum_registry module approach, but it hardly scales if you consider that a large portion of any project is composed of third-party libraries. What if the user of my network protocol intends to marshal PXP trees? I somehow need to fetch the checksums of the PXP modules defining the the relevant type. This is the reason for looking for a solution which integrates with the virtual machine (* i.e. the abstract machine executing the Ocaml program *). However, you are telling me that on this point, the bytecode VM and the native code VM implement two different abstractions. Apparently, what we'll need to do is to better integrate the present md5 digest generation phase with the build process, until our caml breeders will give us type safe marshalling. Alex -- ********************************************************************* http://www.barettadeit.com/ Baretta DE&IT A division of Baretta SRL tel. 02 370 111 55 fax. 02 370 111 54 Our technology: http://www.asxcaml.org/ http://www.freerp.org/