Hi Florian,
> ...
> pygobject GTK3 examples are working. I will experiment and try to
> write Vala/C code that breaks now.
I thought they had Gtk-4 examples as well. But anyway, I cooked a
pygobject version of this drawing-widget example, attached.
Could you:
install pygobject
not sure to understand, i admit i'm testing new things for me , i try to
understand macro syntax and all the stuff... reading
https://www.greghendershott.com/fear-of-macros/index.html
but half (or less) the way.
do you mean just replacing 'list by #'list ?
i do it and it is still working at
> [...]
>
> That should work, but it's also non-hygienic. For example, it will
> be affected if the user does
>
> (let ((list ...))
> (call-your-macro ...))
>
>> and since you use #f in the datum->syntax call, it will also strip away
>> all hygiene annotations from the args-brackets, causing prob
On Mon, May 6, 2024 at 11:41 AM Jean Abou Samra wrote:
> > (with-syntax ((parsed-evaluated-args
> >(datum->syntax #f (cons 'list
> (optimizer-parse-square-brackets-arguments-lister
> > (syntax->datum
> #'args-brackets))
>
> That sh
Hello Basile, thank you for the tips, but I have since managed to get a
good backtrace. -O is what I used by compiling GTK with configure flag
-Dc_args=-O0. -g did not work with g-golf (this is Guix’
with-debug-info transformation), but stripped binaries with debug info
in a separate output and s
about the necessity of 'list it is because
optimizer-parse-square-brackets-arguments-lister return a list like this:
((- 6 4) : (+ i 2)) BUT i suspect ,as in scheme , a bit due to
homoiconicity of lisp/scheme (that represent code and data the same way)
that out of context ((- 6 4) : (+ i 2)) can be
at any point in any scheme if the user write such a thing:
(let ((list 3)) (list 4))
there will be a serious problem
On Mon, May 6, 2024 at 11:41 AM Jean Abou Samra wrote:
> > (with-syntax ((parsed-evaluated-args
> >(datum->syntax #f (cons 'list
> (optimizer-parse-square-brackets
On 5/4/24 11:39 PM, David Pirotte wrote:
Hi Florian,
Hi David, thank you for your continuing responses.
No problem. I am also interested in fixing this bug
I will try to get a backtrace with GTK debug symbols by patching
Guix to add a debug output to GTK, in the hope that I patch the right
David Pirotte writes:
>> (gc-disable) was a smart idea, sadly it does not help, but at least
>> we know now. ...
>
> I am not entirely convinced yet - in one way or another, somewhere,,
> somehow, the klass->snapshot is 'corrupted', either the pointer, or the
> mem it points to ... why, when, wher
> (with-syntax ((parsed-evaluated-args
>(datum->syntax #f (cons 'list
> (optimizer-parse-square-brackets-arguments-lister
> (syntax->datum
> #'args-brackets))
That should work, but it's also non-hygienic. For example, it will
be a
a working solution , but does not know if it follows standards of scheme:
(define-syntax $bracket-apply$
(lambda (stx)
(syntax-case stx ()
;; scheme@(guile-user)> {#(1 2 3 4 5 6 7 8 9)[6 - 4 : 5 + 2]}
;; $bracket-apply$ : parsed-evaluated-args=#
;; $1 = #(3 4 5 6 7)
;; scheme@(guile-user
11 matches
Mail list logo
