Mixp 0.9 available

[Thien-Thi Nguyen]

release notes:

  Tested w/ Guile 2.2.7.

README excerpt:

  Mixp is a Guile interface to expat, James Clark's XML Parser,
  originally written by Thierry Bézecourt.  This release of Mixp is
  available under the terms of the GNU GPL v3 (or later); see COPYING.
  It has been tested with Guile 1.4, 1.8, 2.0, 2.2, and libexpat 2.2.10.

NEWS for 0.9 (2021-12-16):

  - Guile "auto-compilation" suppressed

Env var ‘GUILE_AUTO_COMPILE’ has value "0" during both configure
script operation and "make check".  The Guile-BAUX programs also
set this, so normally "make" should also be covered.

The result: No on-the-fly compilation of .scm to .go files.

  - configure script option ‘--with-expat’ has default

You can use this option to specify a non-standard installation.
Previously, it was required to be given since there was no
default.  Now, if not given, it defaults to the system Expat.

  - configure script errors out if Expat not found

If there is no usable Expat specified or found, the configure
script now fails w/ message "Could not find the Expat library".

  - testing upgraded to support Guile 2.2

For "make check", Guile 2.2 had some issues grokking the
iso-8859-1 encoding in test/x001, but that's now resolved.

  - bootstrap/maintenance tools

upgraded:

 Guile-BAUX 20211208.0839.a5245e7
 GNU gnulib 2021-12-10 21:54:54
 GNU texinfo 6.8
 GNU Automake 1.16.5
 GNU Autoconf 2.71
 GNU Guile 2.2.7

as before:

 (none)

tarball, sig in dir:

  https://download.savannah.nongnu.org/releases/mixp/

-- 
Thien-Thi Nguyen ---
 (defun responsep (query)   ; (2021) Software Libero
   (pcase (context query)   ;   = Dissenso Etico
 (`(technical ,ml) (correctp ml))
 ...))  748E A0E8 1CB8 A748 9BFA
--- 6CE4 6703 2224 4C80 7502



signature.asc
Description: PGP signature

Re: How to capture pid of (system process?

[Jacob Hrbek]

> While Guile does not directly provide a function to get the PID of an 
arbitrary process, we could use pgrep to find what we need. -- Tim


I don't want it to depend on an external commands as the implementation 
is not robust enough for my environment (this codeblock doesn't have to 
be robust, but the project is designed for aviation and i want to do 
similar implementations later for more mission critical functions).


So preferably i need a derivation that integrates with the system and is 
OS independent.


> If you want to do things asynchronuously, you can look at open-pipe. 
It should also be possible to build anything you want with the 
lower-level fork, execl, dup->fdes, ... primitives (assuming things are 
single-threaded). -- Devos


Can you elaborate? (I am noob in guile atm)

- Jacob Hrbek

On 12/14/21 14:25, Maxime Devos wrote:

Jacob Hrbek schreef op ma 13-12-2021 om 21:01 [+]:

I wrote this potato-make 
definition (was simplified):

#:SRC_BEGIN sheme-mode
#!/usr/bin/env sh
exec guile -s "$0" "$@"
!#

(use-modules (ice-9 futures)
   (potato make))
(initialize)

(: "watch" '()
     (~ (do ((i 1 (1+ i)))
        ((> i 6))
      (future (system
       "emacs"))
      ;;(let ((emacs_pid (getpid)))
       ;; (kill emacs_pid SIGTERM)

(execute)
#:SRC_END

expecting to capture emacs's pid and kill it, but the issue is that
using `getpid` gets me the PID of potato-make and `getppid` of the
shell
-> How can i capture just the emacs's pid?

'system' executes the command and waits for it to complete.
After it completed, the process is dead so the pid it used to have is
useless.

If you want to do things asynchronuously, you can look at open-pipe.
It should also be possible to build anything you want with the lower-
level fork, execl, dup->fdes, ... primitives (assuming things are
single-threaded).

Greetings,
Maxime



publickey - kreyren@rixotstudio.cz - 1677db82.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Can guile be implementation independent?

[Jacob Hrbek]

I am used to working with common lisp where i can write code that is
"implementation independent" meaning that following a specific coding
style makes it compatible across multiple interpretators/compilers
(sbcl, LispWorks, etc..)

Is there a way to do the same on GNU Guile? Like writing a code that can
be interpreted by implementations that are following the IEEE 1178-2008
or R7RS standard?

-- Jacob Hrbek



publickey - kreyren@rixotstudio.cz - 1677db82.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: Can guile be implementation independent?

[Nala Ginrut]

Hi Jacob!
You may take a look at akku.scm
You can write r7rs code and use Guile as one of the compiler alternatives.

Best regards.


On Fri, Dec 17, 2021, 09:43 Jacob Hrbek  wrote:

> I am used to working with common lisp where i can write code that is
> "implementation independent" meaning that following a specific coding
> style makes it compatible across multiple interpretators/compilers
> (sbcl, LispWorks, etc..)
>
> Is there a way to do the same on GNU Guile? Like writing a code that can
> be interpreted by implementations that are following the IEEE 1178-2008
> or R7RS standard?
>
> -- Jacob Hrbek
>
>

Re: Can guile be implementation independent?

[Jacob Hrbek]

Looks interesting, are there any known limitations in relation to Guile?

On 12/17/21 03:53, Nala Ginrut wrote:

Hi Jacob!
You may take a look at akku.scm
You can write r7rs code and use Guile as one of the compiler alternatives.

Best regards.


On Fri, Dec 17, 2021, 09:43 Jacob Hrbek  wrote:

I am used to working with common lisp where i can write code that is
"implementation independent" meaning that following a specific coding
style makes it compatible across multiple interpretators/compilers
(sbcl, LispWorks, etc..)

Is there a way to do the same on GNU Guile? Like writing a code
that can
be interpreted by implementations that are following the IEEE
1178-2008
or R7RS standard?

-- Jacob Hrbek


--
-- Jacob Hrbek


publickey - kreyren@rixotstudio.cz - 1677db82.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: Can guile be implementation independent?

[Nala Ginrut]

I'm not sure about the complete incompatibles between Guile and r7rs. To my
experience, the  exception handling is different from r7rs.
I think Scheme community has great progress these years, so many features
are covered by the standard, include FFI(srfi-198),
delimited-continuation(srfi-226), etc.
Guile provides rich features, but people may need to write wrapper for the
standard API.

Best regards.

On Fri, Dec 17, 2021, 11:01 Jacob Hrbek  wrote:

> Looks interesting, are there any known limitations in relation to Guile?
> On 12/17/21 03:53, Nala Ginrut wrote:
>
> Hi Jacob!
> You may take a look at akku.scm
> You can write r7rs code and use Guile as one of the compiler alternatives.
>
> Best regards.
>
>
> On Fri, Dec 17, 2021, 09:43 Jacob Hrbek  wrote:
>
>> I am used to working with common lisp where i can write code that is
>> "implementation independent" meaning that following a specific coding
>> style makes it compatible across multiple interpretators/compilers
>> (sbcl, LispWorks, etc..)
>>
>> Is there a way to do the same on GNU Guile? Like writing a code that can
>> be interpreted by implementations that are following the IEEE 1178-2008
>> or R7RS standard?
>>
>> -- Jacob Hrbek
>>
>> --
> -- Jacob Hrbek
>
>

Re: How to capture pid of (system process?

[Maxime Devos]

Jacob Hrbek schreef op vr 17-12-2021 om 01:32 [+]:
> Can you elaborate? (I am a noob in guile atm)

These procedures are documented in the manual of Guile,
you could look in the source code of Shepherd and Guix
for examples. Most of these procedures are based on POSIX
functions, so you could look at the documentation of the
corresponding POSIX functions for the general concept.

Greetings,
Maxime