From: Catonano <catonano@gmail.com>
To: guile-user@gnu.org
Subject: dynamic-wind
Date: Fri, 30 Jun 2017 22:33:02 +0200 [thread overview]
Message-ID: <CAJ98PDyvUuTTTeSYBJVtRmskiqijLn+cLGCqD18LRboQTY7cbg@mail.gmail.com> (raw)
On the irc channel I was suggested that it might have been a good fit for
my use case
I took a look at it in the manual
I'm perplexed. I don't understand it
How is it supposed to be used ?
The provided example is somewhat contrived, I couldn't understand it anyway.
My use case is basic, really.
I have a scheme wrap around a C library for reading xls files, freexl.
Freexl uses a pointer to a structure tha represents the opened xls file and
its contents
Each function writes/reads in the memory region pointed to such pointer.
In the end, it requires to use a function that closes the file AND frees
all the involved structures in memory.
So my idea was that I would have gotten a simple macro, like this
(with-xls-file "path/to/my/xls-file.xls" handler-ptr
(do-something handler-ptr)
(do-something-more handler-ptr))
and this would have expanded to
(freexl-open "path/to/my/xls-file.xls" handler-ptr)
(freexl-do-something handler-ptr)
(freexl-do-something-more handler-ptr))
(freexl-close handler-ptr)
Do I need dynamic-wind at all ?
next reply other threads:[~2017-06-30 20:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 20:33 Catonano [this message]
2017-06-30 21:48 ` dynamic-wind Panicz Maciej Godek
2017-07-02 6:00 ` dynamic-wind Catonano
2017-07-02 6:01 ` dynamic-wind Catonano
2017-07-02 11:58 ` dynamic-wind Chris Vine
2017-07-05 6:14 ` dynamic-wind Catonano
2017-07-05 8:23 ` dynamic-wind David Kastrup
2017-07-08 20:03 ` dynamic-wind Amirouche Boubekki
2017-07-08 21:34 ` dynamic-wind Marko Rauhamaa
2017-07-09 7:21 ` dynamic-wind David Kastrup
-- strict thread matches above, loose matches on Subject: below --
2017-07-09 12:59 dynamic-wind Chris Vine
2017-07-09 14:09 ` dynamic-wind Vítor De Araújo
2017-07-09 14:49 ` dynamic-wind Chris Vine
2017-07-17 10:04 ` dynamic-wind Catonano
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=CAJ98PDyvUuTTTeSYBJVtRmskiqijLn+cLGCqD18LRboQTY7cbg@mail.gmail.com \
--to=catonano@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).