Hi Manuel, I will try to sort out a small test case; but actually I am sure about the exact and minimum conditions that raise the issue. If few lines can illustrate it, then that may be manageable. Thanks for your support. Regards, Michel.
-----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, October 21, 2016 6:57 AM To: Bruant, Michel Cc: [email protected] Subject: Re: [bigloo] let binding with c Dear Michel, > Hi Bigloo team, > > We observe an issue with the latest bigloo-4.3 (it was already > present in the previous beta) I have a procedure which has a let* . In this > let*, a variable is binded to a C function, something like: > (data (pragma::bstring "string_to_bstring_len( $1, $2 )" [....]) > Then this variable is used in some of the next bindings, and also in the body > of the let*. > But at one stage, (in the body if I remember) ; its content is wrong, > corrupted. > > As a workaround, we needed to change this implementation: > - create a global variable (define data "") ; split the let* into 2 let* and > add a (set! ...) in between to replace the previous binding. > ... something a little bit dirty. > I 'm not sure I can create a small test case to observe this issue; but maybe > this description is enough ? > Anyway, If you can find a fix so that we can remove our workaround, it will > be really appreciated. This should work, normally. I cannot think about an obvious reason for this not to work. Could you give us some additional context? Would you have an actual code excerpt that illustrates the problem? -- Manuel
