From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: mikael@djurfeldt.com
Cc: guile-user <guile-user@gnu.org>
Subject: Re: [ANN] guile-mqtt-0.2.0 released
Date: Sun, 17 Nov 2024 11:39:31 +0100 [thread overview]
Message-ID: <CA+XASoUVPJJd7Lkvj8JyCeVm2qEVdxdFX8L5Guc+XzY0w6AA+w@mail.gmail.com> (raw)
In-Reply-To: <CAA2XvwJV5R1M2_C=e_+d9SCBQ5Gpi87nmyMbCoV0ab5RBsE0Ag@mail.gmail.com>
Hi!
guile-mqtt 0.2.1 now available in macOS via Guile Homebrew
(https://github.com/aconchillo/homebrew-guile):
$ brew tap aconchillo/guile (only needed once)
$ brew install guile-mqtt
On Tue, Nov 12, 2024 at 1:17 AM Mikael Djurfeldt <mikael@djurfeldt.com> wrote:
>
> Guile MQTT provides bindings for the libmosquitto MQTT client
> library. The bindings are written in
> [GOOPS](https://www.gnu.org/software/guile/manual/html_node/GOOPS.html)
> and rely on lower-level bindings created by NYACC directly and
> automatically from mosquitto.h.
>
> Changes compared to v0.1.0:
>
> * All functionality of Chicken Scheme mosquitto bindings now
> implemented and documented.
>
> * Distribute own copy of (... foreign cdata). NYACC is now not
> required if building from a tar archive (as opposed to building from
> a git repository clone).
>
> * Support make in separate build directory.
>
> * Bugfix: unsubscribe now works.
>
> The bindings align with GOOPS style, which means short method
> names. (The specialization is done through the arguments.)
>
> The user can extend the client class by inheritance.
>
> Guile MQTT is free software and is released under the LGPL v3 license; the
> full source distribution is available through
>
> * a tarball:
>
> https://github.com/mdjurfeldt/guile-mqtt/releases/download/v0.2.0/guile-mqtt-0.2.0.tar.gz
>
> * the git repository:
> https://github.com/mdjurfeldt/guile-mqtt
>
> Guile MQTT maturity is beta level.
>
> The following example, as well as the Guile libmosquitto bindings
> themselves,
> are inspired by the [Chicken Scheme mosquitto
> bindings](http://wiki.call-cc.org/eggref/5/mosquitto) by Dmitrii
> Kosenkov.
>
> ```
> (use-modules (mosquitto client))
>
> (let ((client (make-client #:on-connect
> (lambda (client err)
> (if (not (eq? err MOSQ_ERR_SUCCESS))
> (abort err)
> (display "Yay, we are connected!"))))))
> (set! (disconnect-callback client)
> (lambda (client err)
> (if (not (eq? err MOSQ_ERR_SUCCESS))
> (display "Unexpected disconnect..."))))
>
> (set! (message-callback client)
> (lambda (cl msg)
> (display (string->append "Topic: " (topic msg)
> "Payload:" payload msg))
> (publish client "topic2" "message received, thanks!")))
> (connect client "localhost" #:username "mqtt-admin" #:password "mypass")
> (subscribe client "topic1")
> (loop-forever client))
> ```
>
> See further examples under the directory [examples](
> https://github.com/mdjurfeldt/guile-mqqt/tree/main/examples).
next prev parent reply other threads:[~2024-11-17 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 0:16 [ANN] guile-mqtt-0.2.0 released Mikael Djurfeldt
2024-11-17 10:39 ` Aleix Conchillo Flaqué [this message]
2024-11-17 11:36 ` Mikael Djurfeldt
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=CA+XASoUVPJJd7Lkvj8JyCeVm2qEVdxdFX8L5Guc+XzY0w6AA+w@mail.gmail.com \
--to=aconchillo@gmail.com \
--cc=guile-user@gnu.org \
--cc=mikael@djurfeldt.com \
/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).