typing question

typing question

[micha]

Hi,

why is the type of register1  'a -> string but the type of register2
_'a -> string?


cheers
 Michael



let symbol_id = ref 0;;
let register1 fkt =
    let name = "symbol-" ^ (string_of_int !symbol_id) in
    incr symbol_id;
    Callback.register name fkt;
    name
;;

let register2 =
    let symbol_id = ref 1 in
    fun fkt -> let name = "symbol-" ^ (string_of_int !symbol_id) in
    incr symbol_id;
    Callback.register name fkt;
    name
;;

Re: [Caml-list] typing question

[Philippe Wang]

micha wrote:
> Hi,
>
> why is the type of register1  'a -> string but the type of register2
> _'a -> string?
>
>
> cheers
>  Michael
>
>
>
> let symbol_id = ref 0;;
> let register1 fkt =
>     let name = "symbol-" ^ (string_of_int !symbol_id) in
>     incr symbol_id;
>     Callback.register name fkt;
>     name
> ;;
>
> let register2 =
>     let symbol_id = ref 1 in
>     fun fkt -> let name = "symbol-" ^ (string_of_int !symbol_id) in
>     incr symbol_id;
>     Callback.register name fkt;
>     name
> ;;
>   

It is because register2 is detected as an "expansive" expression.

"Expansive expressions" are those that we can't generalize without 
taking the risk to allow type errors at execution, so its type variable 
remains unknown and
can't be "forall 'a. 'a".

Take this simple example :

let x = ref []
So x : '_a ref, because if x were 'a ref, then you could write
x := [343] ; x := ["hello"]
and there would be a type error at runtime.

Thus, even if an expression such as id2 in :
let id x = x ;;
let id2 = id id ;;
does exactly the same computing as id, it can't be 'a -> 'a because id2 
is an "application" and ocaml doesn't generalize applications...

Good luck,

--
 Philippe Wang

Re: Typing question

[Jerome Vouillon]

Hello,

On Mon, Oct 25, 1999 at 05:07:58PM +0200, Sylvain wrote:
> I tried to compile this file "foobar.ml" issuing 
> 
> ocamlc -c -i foobar.ml > foobar.mli
> ocamlc -c -i foobar.mli
> ocamlc -c foobar.ml
> 
> But at the third stage of the process, it answers me that the
> implementation doesn't match the interface ...

The type of a class in not always printed correctly.
In your case, the type of the first class should be :
    class nameTable :
      'a ->
      object
        constraint 'a = #answerToIsNewName
        val fatherContext : 'a
        val table : (string, nameInfo) Hashtbl.t
        method addName : string -> nameType -> unit
        method delName : string -> unit
        method isNewName : string -> bool
        method newName : nameType -> string
      end

-- Jérôme

Re: Typing question

[skaller]

Sylvain wrote:
> 
> Hello,
> 
> I tried to compile this file "foobar.ml" issuing
> 
> ocamlc -c -i foobar.ml > foobar.mli
> ocamlc -c -i foobar.mli

            ^^
            Did you really mean this?

> ocamlc -c foobar.ml
> 
> But at the third stage of the process, it answers me that the
> implementation doesn't match the interface ...
                               Sylvain.Baro@lip6.fr

-- 
John Skaller, mailto:skaller@maxtal.com.au
1/10 Toxteth Rd Glebe NSW 2037 Australia
homepage: http://www.maxtal.com.au/~skaller
downloads: http://www.triode.net.au/~skaller

Re: Typing question

[Sylvain]

Hello,

yes, but the mli file is compiled correctly, but it seems that the cmi
file is no more compatible with the ml file...


> 
> Some time ago i was told that the -i flag not always produce a syntax-correct mli file.
> 
> Friendly,
> 
> Sven LUTHER
> 

-- 

					Sylvain Baro
					Sylvain.Baro@lip6.fr

Re: Typing question

[Sven LUTHER]

On Mon, Oct 25, 1999 at 05:07:58PM +0200, Sylvain wrote:
> Hello,
> 
> I tried to compile this file "foobar.ml" issuing 
> 
> ocamlc -c -i foobar.ml > foobar.mli
> ocamlc -c -i foobar.mli
> ocamlc -c foobar.ml

Some time ago i was told that the -i flag not always produce a syntax-correct mli file.

Friendly,

Sven LUTHER

Typing question

[Sylvain]

Hello,

I tried to compile this file "foobar.ml" issuing 

ocamlc -c -i foobar.ml > foobar.mli
ocamlc -c -i foobar.mli
ocamlc -c foobar.ml

But at the third stage of the process, it answers me that the
implementation doesn't match the interface ...

I joined the file "as is" in the following, because it is a short one.

-- begin --
(* Name server *)

open Hashtbl


exception EmptyContextAllocation
exception NameAlreadyUsed of string


class virtual answerToIsNewName =
  object 
  method virtual isNewName : string -> bool
end

type nameType =
    ConstrName
  | TypeName
  | PredName
  | VarName
  | MuName


type nameInfo =
    { kind : nameType ; num : int}


(* one table because each  number identificator is unique *)
let (numTable : (int,string) t) =
  create 111


let global_name_cpt = ref 0
let gen_new_global () = 
  incr global_name_cpt ; !global_name_cpt




(* one nameTable should be created for each scope *)
class nameTable (fatherContext : #answerToIsNewName) =
  object(self)
  val table  =
    (create 17 : (string,nameInfo) t)

  val fatherContext  = ((fatherContext) : #answerToIsNewName)

 method newName kindOf  =
    ((let newnum = gen_new_global ()
    in
    let newname = string_of_int newnum (* Temporaire *)
    in
    let register () = 
      add numTable newnum newname ;
      add table newname {kind = kindOf ; num = newnum}
    in
    try
      find table newname ; 
      self#newName kindOf
    with Not_found ->
      (register () ; newname)) : string)
          


  method isNewName n = 
    try 
      find table n ; false
    with Not_found -> fatherContext#isNewName n


  method addName name kindOf =
    let newnum = gen_new_global ()
    in
    let register () = 
      add numTable newnum name ;
      add table name {kind = kindOf ; num = newnum}
    in
    try
      find table name ; 
      raise (NameAlreadyUsed name)
    with Not_found ->
      register ()
   
  method delName name =
    remove table name

end


class emptyContextClass =
  object
  method newName (x : nameType) = ((raise EmptyContextAllocation) :
string)
  method isNewName (s : string) = true
  method addName (n:string) (k:nameType) = 
    ((raise EmptyContextAllocation) : unit)

end

let emptyContext = new emptyContextClass


-- end --

Thank you.

-- 

					Sylvain Baro
					Sylvain.Baro@lip6.fr