ok thanks you i hope the real bug in bigloo will be resolved because it's a nice tool. Damien
Le Wednesday 19 October 2016 10:50:15 Laurent Bloch, vous avez écrit : > Hi, > > Le mercredi 19 octobre 2016 Damien MATTEI a écrit ceci : > > > i'm using bigloo4.2c and have had a similar issue last year,i'm using > > bigloo with the java option enabled to generate JVM byte code and i noticed > > that > > when creating string variables with nested define in function ,the code : > > > > (define (ResultatMesuresFbeta bstr_identificateur bstr_objet) > > > > (display-var-nl "BiglooCode.scm :: ResultatMesuresFbeta :: > > bstr_identificateur = " bstr_identificateur) > > (display-var-nl "BiglooCode.scm :: ResultatMesuresFbeta :: bstr_objet = " > > bstr_objet) > > > > (define len_bstr_identificateur (byte*-length bstr_identificateur)) > > (display-var-nl "BiglooCode.scm :: ResultatMesuresFbeta :: > > len_identificateur = " len_bstr_identificateur) > > (display-var-nl "BiglooCode.scm :: ResultatMesuresFbeta :: (string? > > bstr_identificateur) = " (string? bstr_identificateur)) > > > > (define identificateur (make-string len_bstr_identificateur)) > > ;;(define objet "") > > > > (set! identificateur bstr_identificateur) > > ;;(set! identificateur (string-append bstr_identificateur)) > > > > ;;(display-var-nl "BiglooCode.scm :: ResultatMesuresFbeta :: > > (string-append \"\" bstr_identificateur) = " (string-append "" > > bstr_identificateur)) > > ;;(set! objet bstr_objet) > > Hum, as far as I remember, nested define are only allowed at the > beginning of a body... > > Cheers! > -- [email protected], [email protected], UNS / OCA / CNRS
