Sven <luther@dpt-info.u-strasbg.fr> writes:

[...]

> > But what if you compile only one module ? If you compile a.ml ocamlc -c
> > -o unnom.cmo a.cmo will act like ocamlc -pack -o unnom.cmo -c a.cmo and
> > i will have to access the A module through Unnom.A which is very
> > disturbing, isn't it ?
> 
> Well, no, it would be used by default only when building libraries (.cma
> and such).

This makes more sense when limiting this behaviour to libraries

[...]

> > I cannot understand why you wish a so strange behaviour, and
> 
> Does it makes more sense if limited to libraries ?

Yes it does !


[...]

> Like i said before, because the enabling by default is only for building
> .cmas. Sorry about the confussion.

Confussion has been wiped out :)

[...]

> > This sounds hairy (i mean: i am frightened !) ! 
> 
> Yes, sure, better to have it all work for all plateforms ...
> 
> > How can you write Makefile that can compile an application on any
> > installation, when the change you eask about is applied (if i understand
> > it). 
> 
> With conditional rules depending on the result of ocamlc -pack-default
> or something such ?

This will lead users to write more advanced makefile stuff, they will not
necessarily bother.

> > you determine if the default behaviour is to pack or not to
> > you set a variable OCAMLC according to what you expect the compiler to do.
> > you use the OCAMLC variable in the place of `ocamlc' program
> 
> Or like that also, but the definition of OCAMLC could be conditional.
> And anyway, it would be ocamlmklib which we redefine.

Oc.


[...]

> Ok, i hope this mail will lift the misunderstanding now.

It did !
> 
> Friendly,

Bye !
-- 
Michaël Grünewald <michael-grunewald@wanadoo.fr>  - RSA PGP Key ID: 0x20D90C12
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners