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
Re: [Caml-list] XML, XSL, eXcetera
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Alessandro Baretta <alex@b...>
Subject: Re: [Caml-list] XML, XSL, eXcetera
First of all, let me excuse myself for having been away from 
this discussion for a couple of days, but I could not help 
it. The cause, unfortunately, is a tragedy which hit me 

Stefano Zacchiroli wrote:
> Sure, it's named "/usr/bin/ocaml" :-)
> Try this script:
>   #!/usr/bin/ocamlrun /usr/bin/ocaml
>   print_endline "Hello, world!"
> You can use all toplevel directives so you can also use libraries that
> support dynamic loading. BTW, if you want to use a library that doesn't
> support dynamic loading you have to use a relinked ocaml interpreter or
> you will be in trouble.
> Maybe I've misunderstood your question ...
> Cheers.

I was thinking about something more specific to XML 
processing. Something like a application/processing server 
to be connected with Apache and the like. Such a process 
would have to listen on a socket for connections from 
clients requesting the processing of <?ocaml ...?> tags or 
of an otherwise specified ocaml expression. I am now 
thinking that maybe this would be overshooting the mark 
here, if we are simply thinking of integrating O'Caml code 
in XSLT stylesheets, where the processor is an O'Caml 
application. In this case, one could conceivably link the 
toplevel into the XSLT processor. As an XSLT template is 
activated, if there is any O'Caml code associated with it, 
the processor could just pass it to the "virtual" toplevel 
within it for immediate excecution.


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