From: Emmanuel CHAILLOUX <Emmanuel.Chailloux@lip6.fr>
To: caml-list@pauillac.inria.fr
Subject: Re: Very very short question on objects
Date: Mon, 25 Oct 99 22:33:46 +0200 [thread overview]
Message-ID: <199910252033.WAA01700@micmac.lip6.fr> (raw)
In-Reply-To: <19991025114616.B226@jones.int-evry.fr>
Hi Christian,
> Hi everybody,
>
> I'm getting started with OCaml objects and, trying to compose
> functional updates, I ran into something like the following
> toy example:
>
> Objective Caml version 2.02
>
> # class x > object
> method private f = ()
> method g = {< >} # f
> end
> ;;
> class x : object method f : unit method g : unit end
> #
>
> Method [f] is not private... Shouldn't be this an error?
Because you add a type constraint as follow :
$ ocaml
Objective Caml version 2.02
class t = object(self :'a)
constraint 'a = < f : unit; ..> (* from {<>}#f *)
method private f = ()
method g = {<>}#f
end;;
class t : object method f : unit method g : unit end
If you have in the same class declaration, a method f with the attribute private, and the same method f without it, the
last definition wins.
# class d = object method private f = print_string "private" method f = print_string "public" end;;
class d : object method f : unit end
# let q = new d;;
val q : d = <obj>
# q#f;;
public- : unit = ()
including the case where the last declaration is private.
# class e = object method f = print_string "public" method private f = print_string "private" end;;
class e : object method f : unit end
# let i = new e;;
val i : e = <obj>
# i#f;;
private- : unit = ()
So the last declaration wins, includind a "private" declaration.
The other examples show some type constraints :
(* don't copy the instance to keep private method *)
# class y = object(self) method private f = () method g = self#f end;;
class y : object method private f : unit method g : unit end
(* It's same that your example *)
# class z = object(self) method private f = () method g = (Oo.copy self)#f end;;
class z : object method f : unit method g : unit end
(* Another case to add a type constraint (for the parameter o) *)
# class u o = object(self:'a) method private f = () method g (o : 'a) = o#f end;;
class u : 'b -> object ('a) method f : unit method g : 'a -> unit end
(* to see an inherited private method *)
# class v = object(self) inherit y as super method f = super#f end;;
class v : object method f : unit method g : unit end
If you want to simulate the attribute "private", you can use a functional instance variable as follows :
# class p (h : 'b) = object (self : 'a)
constraint 'b = 'a -> unit
val f = h
method g = f({<>})
end;;
class p : ('a -> unit) -> object ('a) val f : 'a -> unit method g : unit end
# let h x = ignore(Oo.copy x); ();;
val h : < .. > -> unit = <fun>
# let ip = new p h;;
val ip : p = <obj>
# ip#g;;
- : unit = ()
> Best regards,
>
> Christian
Best regards,
Emmanuel...
prev parent reply other threads:[~1999-10-26 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-25 9:46 Christian RINDERKNECHT
1999-10-25 19:31 ` William Chesters
1999-10-25 20:33 ` Emmanuel CHAILLOUX [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199910252033.WAA01700@micmac.lip6.fr \
--to=emmanuel.chailloux@lip6.fr \
--cc=caml-list@pauillac.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).