unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Damien Mattei <damien.mattei@gmail.com>,
	Taylan Kammer <taylan.kammer@gmail.com>
Cc: Jean-Paul Roy <jean-paul.roy@unice.fr>,
	guile-devel <guile-devel@gnu.org>
Subject: Re: new function
Date: Thu, 23 Sep 2021 20:00:15 +0200	[thread overview]
Message-ID: <702b197719f098262a424608fb134f218af635a9.camel@telenet.be> (raw)
In-Reply-To: <CADEOadePDXQJZgQJG1oK9Bj16EaY2zGs+OBYauj=E0sUf8Pg9g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5688 bytes --]

Damien Mattei schreef op do 23-09-2021 om 19:27 [+0200]:
> yes i know parsing the whole code is the only portable solution, but it is slow,even on a few dozen of lines the slowing is visible ,so i can even think of that on one thousand lines...
> 
> I finally succeed in Guile with simple piece of code to make my example run with a single assignment operator <-  , here i define for variable the assignment operator <$ , <- is working with arrays too:
> 
> Preview:
> 
> (define-syntax <$
>   
>   (lambda (s)
>     
>     (syntax-case s ()
>       
>       ((_ var value)
>        
>        (case (syntax-local-binding #'var)
> 	 
>          ((lexical) #'(begin
> 			(display "<$ : lexical scope : ")
> 			(display (quote var))
> 			(newline)
> 			(set! var value)))
> 	 
> 	 ((displaced-lexical) #'(begin
> 				  (display "<$ : displaced-lexical scope : ")
> 				  (display (quote var))
> 				  (newline)
> 				  (set! var value)))
> 	 
>          ((global) #'(begin
> 		       (display "<$ : global scope : ")
> 		       (display (quote var))
> 		       (newline)
> 		       (define var value)))
> 	 
>          (else #'(begin
> 		   (display "<$ : unknow variable scope :")
> 		   (display (quote var))
> 		   (error "<$ : unknow variable scope : "))))))))
> 
> 
> it allows this Scheme+ code to run with a single assignment operator (note in some case the operator is also a definition of variable,but it is invisible for the programmer, it has the duality of define and set!):
> 
> Preview:
> 
> (define (subset-sum-guile L t)
> 
>   {ls <- (length L)}
>   {dyn <- dyna[ls t]}
> 
> ;; dyna[ls][t] means 0: unknown solution, 1: solution found, 2: no solution
>   
>   (condx [{dyn <> 0} (one? dyn)]
> 	 [(null? L) {dyna[ls t] <- 2}  #f] ;; return #f
> 	 
> 	 [exec {c <- (first L)}]	 
> 	 ;; c is the solution
> 	 [{c = t} {dyna[ls t] <- 1}  #t]  ;; return #t
> 	 
> 	 [exec {R <- (rest L)}]	 
> 	 ;; continue searching a solution in the rest
> 	 [{c > t} {s <- (subset-sum-guile R t)}
> 	          {dyna[ls t] <- (one-two s)}
> 		  s] ;; return boolean value
> 			
> 	 ;; else : c < t at this point
> 	 ;; c is part of a solution OR not part of a solution
> 	 [else {s <- {(subset-sum-guile R {t - c}) or (subset-sum-guile R t)}}
> 	       {dyna[ls t] <- (one-two s)}
> 	       s])) ;; return boolean value
> 
>      
> 
> some people were sceptic about the possibility to make it, but it works, i do not say it is portable code.
> 
> When i run the program with debug i see that:
> scheme@(guile-user)> (subset-sum-guile  L-init t-init)
> <$ : global scope : ls
> <$ : global scope : dyn
>  
> <$ : global scope : c
> <$ : global scope : R
> <$ : global scope : s
> <$ : global scope : ls
> <$ : global scope : dyn
>  
> <$ : global scope : c
> .... hundreds of lines.....
> #t
> 
> all variable are global,

No, they are local, even though syntax-local-binding returns 'global'.
'syntax-local-binding' doesn't know we will be defining a local variable
with the same name later, so it says 'global' instead of 'lexical' or
'displaced-lexical'.

There is no such thing as ‘global to the body of the function’, what you are
descrbing is local variables.

The macro <$ you have defined won't work for the "hello world" example I sent
you:

(define (#{hello/won't-work}# language)
  (cond ((equal? language "dutch")
         (<$ message "Hallo wereld"))
        ((equal? language "english")
         (<$ message "Hello world")))
  (display message)
  (newline))
While compiling expression:
Syntax error:
unknown file:70:9: definition in expression context, where definitions are not allowed, in form (define message "Hallo wereld")

The following does, however:

(define (hello language)
  (<$ message #f)
  (cond ((equal? language "dutch")
         (<$ message "Hallo wereld"))
        ((equal? language "english")
         (<$ message "Hello world")))
  (display message)
  (newline))

Possibly this limitation of <$ is acceptable to you though.

> but they are just global to the body of the function,not at toplevel,so there is no risk of breaking the code logic it is just that if we want to see lexical scope we need a more nested example,it is strange because i thought that the condx macro creates nestled code for each conditional clauses...
> 
> to see the lexical scope we can use this example:
> scheme@(guile-user)> 
> (condx [exec {k <- 1}]
>     [{k = 1} {k <- {k + 1}} {k + 1}]
>     [else 'never])
> <$ : global scope : k
> <$ : lexical scope : k
> $3 = 3
> here the lexical scope is well visible :-)
> but if k had existed at toplevel it is not modified :-( :
> scheme@(guile-user)> (define k 0)
> scheme@(guile-user)> 
> (condx [exec {k <- 1}]
>            [{k = 1} {k <- {k + 1}} {k + 1}]
>            [else 'never])
> <$ : global scope : k
> <$ : lexical scope : k
> $4 = 3
> scheme@(guile-user)> k
> $5 = 0
> 
> :-(
>  probably beause syntax-local-binding only works in the current lexical environment ?
> https://www.gnu.org/software/guile/docs/master/guile.html/Syntax-Transformer-Helpers.html
> but not at toplevel ???
> Scheme Procedure: syntax-local-binding id [#:resolve-syntax-parameters?=#t]
> Resolve the identifer id, a syntax object, within the current lexical environment
> 
> for this reason i still searching a solution that would be a mix of syntax-local-binding and Module System Reflection .

Use the second return value of syntax-local-binding.
Or just use set! instead of <$ and <- to modify global variables,
and use <- and <$ for local variables only.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-09-23 18:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19  7:54 new function Damien Mattei
2021-09-19 14:41 ` Matt Wette
2021-09-19 14:43   ` Matt Wette
2021-09-19 21:38 ` Taylan Kammer
2021-09-21 12:26   ` Damien Mattei
2021-09-22  8:44   ` Damien Mattei
2021-09-22  9:06     ` William ML Leslie
2021-09-22  9:53       ` Damien Mattei
2021-09-22 18:51         ` Taylan Kammer
2021-09-22 21:52           ` William ML Leslie
2021-09-23  8:40             ` Damien Mattei
2021-09-23 19:03             ` Taylan Kammer
2021-09-23 17:27           ` Damien Mattei
2021-09-23 18:00             ` Maxime Devos [this message]
2021-09-23 20:27             ` Taylan Kammer
2021-09-23 20:42               ` Damien Mattei
2021-09-23 20:48               ` Taylan Kammer
2021-09-23 21:53                 ` Damien Mattei
2021-09-24  4:41                   ` Damien Mattei

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=702b197719f098262a424608fb134f218af635a9.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=damien.mattei@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=jean-paul.roy@unice.fr \
    --cc=taylan.kammer@gmail.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).