Re: [Caml-list] question: what is the recommended use case of `val` in class type

[Goswin von Brederlow <goswin-v-b@web.de>]

On Sun, Jul 03, 2016 at 03:23:35PM +0900, Jacques Garrigue wrote:
> Hi Hongo,
> 
> You may want to have a look at a small camlp4 syntax extension I wrote a long time ago,
> which allows to do what you say.
> Using it, one would write:
> 
>      val mutable x with accessor
> 
> to say that it can be accessed through the x and x_set methods.
> 
> The code is here:
> http://www.math.nagoya-u.ac.jp/~garrigue/code/ocaml.html
> 
> Note that I didn’t try to support functional state changes, i.e. adding a method
>     method x_upd x’ = {< x = x’ >}
> 
> Jacques

What's the point of x then? Wouldn't it make more sense to only expose
the accessors so even derived classes will go through them instead of
accessing x directly?

Question: Can ppx attributes generate the accessors but also hide the
"val mutable x" when no mli file is present?

MfG
	Goswin