Re: [Caml-list] Problems with printing MetaOCaml generated code

[Jacques Carette <carette@mcmaster.ca>]

But that's the whole point: you are not persisting a value, you are 
persisting a local variable.

In the context of staging, a variable and its value are radically 
different, unlike in the traditional functional programming context, 
where this difference can be safely and harmlessly blurred.

If you want to persist "named values", then give globally accessible 
names to these values [which I believe others have already told you].  
If you want to persist values, then use my solution or a variant of that.

Jacques

On 2015-05-02 9:56 PM, Ömer Sinan Ağacan wrote:
> That's not a solution. I should be able to generate some values in
> code generation time and persist them in code values, that's the whole
> point here.
>
> 2015-05-02 16:49 GMT-04:00 Jacques Carette <carette@mcmaster.ca>:
>> try instead
>>     let stx1 = .< A >. in
>> and then
>>     print_code std_formatter .< .~stx1 >. ;
>>
>> That ought to work as you wish.
>>
>> Jacques
>>
>>
>> On 2015-05-02 2:45 PM, Ömer Sinan Ağacan wrote:
>>> In case anyone's still interested, I produced a very simple example that
>>> demonstrates the issue:
>>>
>>>     ➜  metaocaml_serialization_issue git:(master) ✗ ls
>>>     Main.ml  Syntax.ml
>>>     ➜  metaocaml_serialization_issue git:(master) ✗ cat Syntax.ml
>>>     type stx =
>>>       | A
>>>       | B of stx
>>>       | C of (stx * stx)
>>>     ➜  metaocaml_serialization_issue git:(master) ✗ cat Main.ml
>>>     open Format
>>>     open Print_code
>>>     open Runcode
>>>     open Syntax
>>>
>>>     let _ =
>>>       let stx1 = A in
>>>       let stx2 = B A in
>>>       let stx3 = C (A, A) in
>>>
>>>       print_code std_formatter .< stx1 >.;
>>>       print_code std_formatter .< stx2 >.;
>>>       print_code std_formatter .< stx3 >.;
>>>
>>>       print_closed_code std_formatter (close_code .< stx1 >.);
>>>       print_closed_code std_formatter (close_code .< stx2 >.);
>>>       print_closed_code std_formatter (close_code .< stx3 >.);
>>>     ➜  metaocaml_serialization_issue git:(master) ✗ metaocamlc Syntax.ml -c
>>>     ➜  metaocaml_serialization_issue git:(master) ✗ metaocamlc
>>> Syntax.cmo Main.ml -o main
>>>     ➜  metaocaml_serialization_issue git:(master) ✗ ./main
>>>     .<(* CSP stx1 *) Obj.magic 0>. .<(* CSP stx2 *)>. .<(* CSP stx3 *)>. .<
>>>     (* CSP stx1 *) Obj.magic 0>. .<(* CSP stx2 *)>. .<(* CSP stx3 *)>.
>>>     ➜  metaocaml_serialization_issue git:(master) ✗
>>>
>>>
>>> 2015-05-01 12:53 GMT-04:00 Ömer Sinan Ağacan <omeragacan@gmail.com>:
>>>>> You can't serialize `eval_ref` as `eval_ref` because that is a local
>>>>> identifier. If you print out `eval_ref` into some other ml file and
>>>>> compiler
>>>>> it, it is going to give an "Unbound identifier eval_ref" error.
>>>> That's true. Just to make sure and make the output more clear, I moved
>>>> the
>>>> relevant code to another module, and now it's printing this:
>>>>
>>>> .<Unlambda.eval_ref (* CSP p' *) []>.
>>>>
>>>> My main question is that it should serialize p' here, but it doesn't. I'm
>>>> trying to understand why.
>>