[Erlhive-devel] newest stuff in trunk

[Ulf W. <ul...@wi...>]

I've finally committed my latest stuff to trunk

svn co http://erlhive.svn.sourceforge.net/svnroot/erlhive/trunk

Perhaps the biggest change is that I've started building on
a erlhive/src/otp directory, currently with the following contents:

erlhive_compile.erl
erlhive_epp.erl
erlhive_file.erl
erlhive_file_io_server.erl
erlhive_file_server.erl
erlhive_ftp.erl
erlhive_gen.erl
erlhive_gen_server.erl
erlhive_gen_tcp.erl
erlhive_io.erl
erlhive_os.erl
erlhive_prim_file.erl
erlhive_proc_lib.erl

The file and io stuff works, practically all of it.
You can read other users' files, by addressing them
as /erlhive/User/... This is akin to reading public data from
another user. Anything you put under /tmp will be removed
when the transaction terminates. (:

I've not yet quite figured out erlhive_compile, so it's just
a copy of the original compile.erl. My idea is that you should
be able to call compile:file(...) from the erlhive shell, and have
erlhive automatically compile, transform, and output beam
files to the "erlhive file system". The FTP support will work
for fetching files from another FTP server. This could be used
as a convenient way to bring code into your erlhive account.

epp works in erlhive, though, FWIW. I have this hope that I will
be able to move over entirely to file-based compile and load,
but I have to figure out how to best avoid subversion (loading
a module that hasn't been safe-compiled). The answer is
probably attributes - since all files in erlhive are actually
database objects, you can attach attributes to them, and
erlhive has a set of "automatic" attributes that can't be
modified by user code.

I will not swear that all of this works right now. I've been a bit
too busy to play with it lately.

Oh, and I put a link to the Erlhive Wiki on the web page.

BR,
Ulf W