From: Mortimer Cladwell <mbcladwell@gmail.com>
To: guile-user@gnu.org
Subject: Re: can't export conditional variable set with 'cond'
Date: Fri, 2 Feb 2024 03:15:16 -0500 [thread overview]
Message-ID: <CAOcxjM52LA1m7npEXvrPbqYPhOxF6Em1exiE0S1cUYSHJDmsyQ@mail.gmail.com> (raw)
Thanks all.
Both parameters and boxes work for me with guile-3.0.9, which is what I run
on my local machine.
>> I get the impression that you were asking this more for curiosity about
how the language implementation works than to solve a problem
I am trying to solve a problem. I have old code running on a remote server
using guile-3.0.5. When I pull to local (guile-3.0.9) that code no longer
works using 3.0.9. I find the problem is that globals are not properly
exported. If I run my original test code on the server - works fine
(without boxes, parameters). To clarify I am using:
-------------testexport.scm begin----------------------------------
(define-module (testexport)
#:use-module (ice-9 pretty-print)
#:use-module (env)
)
(define (main)
(pretty-print (string-append "varA in main: " varA))
(pretty-print (string-append "varB in main: " varB))
(pretty-print (string-append "varC in main: " varC))
)
(main)
-------------testexport.scm end----------------------------------
------------env.scm begin-----------------------------------
(define-module (env)
#:use-module (ice-9 pretty-print)
#:export(varA varB varC))
(define varA "A")
(define varB "")
(define varC "")
(define testval "x")
(cond
((string= testval "x") (set! varB "B"))
((string= testval "y") (set! varB "error"))
((string= testval "z") (set! varB "null"))
)
(pretty-print (string-append "varB post cond: " varB))
(if (string= testval "x") (set! varC "C"))
(pretty-print (string-append "varC post if: " varC))
-------------env.scm end----------------------------------
remote server running guile 2.2.7:
admin@ip-172-31-16-153:~/testexport$ guile -L . ./testexport.scm
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /home/admin/testexport/./testexport.scm
;;; compiling ./env.scm
;;; compiled
/home/admin/.cache/guile/ccache/2.2-LE-8-3.A/home/admin/testexport/env.scm.go
"varB post cond: B"
"varC post if: C"
;;; compiled
/home/admin/.cache/guile/ccache/2.2-LE-8-3.A/home/admin/testexport/testexport.scm.go
"varA in main: A"
"varB in main: B"
"varC in main: C"
admin@ip-172-31-16-153:~/testexport$ guile -v
guile (GNU Guile) 2.2.7
Copyright (C) 2020 Free Software Foundation, Inc.
License LGPLv3+: GNU LGPL 3 or later <http://gnu.org/licenses/lgpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
-----------------------------------------------------------------
remote server running guile-3.0.5:
admin@ip-172-31-16-153:~/testexport$
/gnu/store/q8brh7j5mwy0hbrly6hjb1m3wwndxqc8-guile-3.0.5/bin/guile -L .
./testexport.scm
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-auto-compile argument to disable.
;;; compiling /home/admin/testexport/./testexport.scm
;;; compiling ./env.scm
;;; compiled
/home/admin/.cache/guile/ccache/3.0-LE-8-4.4/home/admin/testexport/env.scm.go
"varB post cond: B"
"varC post if: C"
;;; compiled
/home/admin/.cache/guile/ccache/3.0-LE-8-4.4/home/admin/testexport/testexport.scm.go
"varA in main: A"
"varB in main: B"
"varC in main: C"
next reply other threads:[~2024-02-02 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 8:15 Mortimer Cladwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-23 13:37 can't export conditional variable set with 'cond' Mortimer Cladwell
2024-01-23 14:22 ` Damien Mattei
2024-01-24 20:07 ` Skyler Ferris
2024-02-01 12:06 ` Daniel Meißner
2024-02-01 14:53 ` M
2024-02-02 0:13 ` Skyler Ferris
2024-02-02 0:00 ` Skyler Ferris
2024-02-02 0:16 ` M
2024-02-02 0:25 ` Skyler Ferris
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOcxjM52LA1m7npEXvrPbqYPhOxF6Em1exiE0S1cUYSHJDmsyQ@mail.gmail.com \
--to=mbcladwell@gmail.com \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).