Extended draft paper submission: SETP-09 call for papers
This Extended Call for Papers is for those who didn't get a chance to submit
the papers for the earlier call for papers. The papers received and accepted in
response to this extended call for papers will be included in the final version
Dear list members,
Tomorow Monday is the last day to register on the TYPES 2009 website if
you want to pay reduced fee. Later registration is still possible and
talk submission to. We will probably (as every year) publish post
proceedings with good referee.
The TYPES workshop cover theory
Ashish Agarwal wrote:
The module type exists, it's just that it doesn't have a name.
Right, thanks for the clarification.
let x = (123, abc)
does not define type x = int * string either.
True, but I think the expectations are different for module types. A
file a.ml http://a.ml
Jon Harrop j...@ffconsultancy.com writes:
On Sunday 19 April 2009 22:36:12 Ashish Agarwal wrote:
Having the compiler introduce module type names automatically from mli
files would be very helpful, and I don't see any disadvantages.
Some people contest the idea that files should automatically
Martin Jambon martin.jam...@ens-lyon.org writes:
OK, but I think the real issue is inheritance. In order to truly extend an
existing module, one needs to access the private items of the inherited module
implementation. In order to avoid messing up with the original module's
global
Arkady Andrukonis grazingc...@yahoo.com writes:
Hi,
I would like to find the easiest block structure to represent nested leaves
and nodes in a tree structure that works for OCaml. In Common Lisp there is
the help of indentation, but I haven't found one for OCaml.
We have one parent node
From: Guillaume Hennequin gje.henneq...@gmail.com
Dear list,
this is a somewhat naive question
let's define
class a = object
val mutable v = ...
method v = v
method m = something that uses v
end ;;
now assume that I want to create a lot of those a objects, so many that I
may
