module system / (oop goops) / :duplicates (merge-generics) / bug?

Hello, Can someone kindly look at this small example and tell me what's wrong? I get this david@rascar:~ 8 $ guile GNU Guile 2.0.0.160-39be ... scheme@(guile-user) (use-modules (mg-3)) (letstry) mg-3.scm:17:2: In procedure letstry:

Fw: manual - small typo error

) #:use-module (math 3D-vectors) #:duplicates (merge-generics)) Cheers, David ;; -- Begin forwarded message: Date: Tue, 5 Jul 2011 19:13:48 -0300 From: David Pirotte da...@altosw.be To: bug-guile@gnu.org Subject: manual - small typo error Hello, reporting a small typo error in section

(ice-9 format) and :duplicates (merge-generics) / bug

a new prompt. Type `,bt' for a backtrace or `,q' to continue. scheme@(guile-user) [1] Cheers, David. ;; -- Begin forwarded message: Date: Tue, 5 Jul 2011 18:43:41 -0300 From: David Pirotte da...@altosw.be To: bug-guile@gnu.org Subject: Fw: module system / (oop goops) / :duplicates (merge-generics

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hello Ludovic, david@rascar:~ 8 $ guile GNU Guile 2.0.0.160-39be I think commit ad4bd7c2c0c931a91160772e5ebf40af0f471874 (in 2.0.2) fixes this. Can you check with 2.0.2? [I should have pulled the latest off course, I am sorry] I slightly modified the mg-*.scm files:

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hello Andy, Ludovic, ... (define-module (mg-1) :use-module (oop goops) :duplicates (merge-generics) :export (widget-a dialog )) Here the #:duplicates is unnecessary, because you are not importing any duplicate bindings. Yes, I think our messages

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hello Andy, Invoke: (default-duplicate-binding-handler '(merge-generics replace warn-override-core warn last)) This is not 'so important' anymore, but for bug tracking purposes, please note that adding the above in my init.scm file and commenting the #:duplicates (...) expression

vm-error: guile-gnome-2 / treeview / 'button-press-event

Hello, GNU Guile 2.0.2.7-ae88d g-wrap / git-clone / v1.9.13-13-geeb1aae guile-cairo / bzr-clone guile-gnome-platform / git-clone / 0.8.0-9-gb3ae01e The attached code [which worked under guile-1.8 and guile-gnome .deb packages] gives me the following error when

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hi Andy, (default-duplicate-binding-handler '(merge-generics replace warn-override-core warn last)) This is not 'so important' anymore, but for bug tracking purposes, please note that adding the above in my init.scm file and commenting the #:duplicates (...) expression

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hi Andy, Ah, funny, I thought the version would always correspond to what you had. But that is not the case: wingo@badger:~/src/guile$ git describe v2.0.2-7-gae88d9b wingo@badger:~/src/guile$ meta/guile GNU Guile 2.0.2.4-c1e3e I guess what I meant was that you needed a newer

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hi Andy, Ludovic, Any news about the following problem I reported ? I am kindly pinging you both, as it is very difficult to [smoothly] work with goops until this problem is solved - unless, on purpose, you do not give identical names to any slot pertaining to different classes, but this is

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hi Andy, Le Thu, 18 Aug 2011 13:01:34 +0200, Andy Wingo wi...@pobox.com a écrit : Hi David, I fixed it! Thank you very much! The examples I sent earlier now all work, but I still have a problem when running my app [the app is working perfectly if I name differently all exported slot

goops: make 'allowing' the use of non existing init kw or slot

Hello, The attached code speaks for itself: shouldn't we get an error on both of these attempts? 1] the slot exists but no :init-keyword was defined; 2] the slot does not exists. Cheers, David (define-module (goops-make-using-non-existing-kw-or-slot) :use-module

goops: default-duplicate-binding-handler 'does not work' when global [i.e. in init.scm]

Hello, I've noticed that the following attached code [slightly modified since my previous related message] only works if the third module also specify: :duplicates (merge-generics replace warn-override-core warn

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hi Andy, Ludovic, I fixed it! Thank you very much! The examples I sent earlier now all work, but I still have a problem ... I finally could reproduce the problem and wrote an example you can run 'in the cafe without internet' :) [hopefully] in addition to the comments here

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

2011 14:05:18 -0300, David Pirotte da...@altosw.be a écrit : Hi Andy, Ludovic, I fixed it! Thank you very much! The examples I sent earlier now all work, but I still have a problem ... I finally could reproduce the problem and wrote an example you can run 'in the cafe without

Re: module system / (oop goops) / :duplicates (merge-generics) / bug?

Hi Andy, ... Well. This was indeed an amusing issue :) I am indeed sitting in the café, and so thank you :) However right now I trust Guile more than I trust Guile-GNOME, so an more minimal case is even better :) Like this: Yes, of course: it took me a while to understand what could be

bug#10567: Fw: guile-library - make bug report

I sent the following bug report to guile-devel by mistake, sorry ;; -- Hello, guile 2.0.3.150-88c0 guile-lib release-0.2.1-2-ge9fe22b ... make[1]: Entering directory `/usr/local/src/guile-lib/git-clone/src' ../dev-environ /usr/local/bin/guile-tools compile -o

bug#10567: Fw: guile-library - make bug report

Hi Andy, The line in question: (eq? (car rest) ':) It seems you have (read-set! keywords 'prefix) in your init.scm, which affects the compile-time environment. Yes I do, sorry i din't think of that but i confirm it is the case. ... Cheers, David Aside, I always

bug#11885: guile-2.0.6 1 of 1 test failed

Hi Dennis, This is not going well at all : $ dpkg -S /usr/lib/libgc.so ... try this: dpkg -l | grep libgc1c2 dpkg -l | grep libgc-dev i am on testing and the answers here are 7.1-8. if these packages are not installed, or if the -dev is not installed, do install

bug#12789: threads - proc-map - multicore issue

Hello, in the following example, the cores, 4 in my case, are used for a couple of seconds, then at some point only one core is used: guile -c '(begin (use-modules (ice-9 threads)) (par-map 1+ (iota 40)))' Cheers, David

bug#14080: Guile bug building from source with pkg-config

Hello Mark(s) :) Also, what version of g-wrap are you trying to build? Note that in order to build guile-clutter, you also need the following dependencies to be satisfied [i'm using git, so this is an extract from the README file of the clutter branch of guile-gnome-platform]

bug#14756: threads - par-map - multicore issue

Hello, guile --version guile (GNU Guile) 2.0.9.20-10454 It seems that the par-map not using all cores problem has some how been reintroduced? guile -c '(begin (use-modules (ice-9 threads)) (par-map 1+ (iota 40)))' only uses 1 core [it seems it uses some other

bug#15683: [critical] ERROR: ... close-pipe: pipe not in table

Hello guilers, GNU Guile 2.0.9.20-10454 [cfr irc chat of October the 17th, 2013] I am facing a bug that only occurs on extremely powerful servers: in ice-9/popen.scm: 106: 1 [close-pipe #input: #{read pipe}# 69] In unknown file: ?: 0 [scm-error

bug#15683: [critical] ERROR: ... close-pipe: pipe not in table

Hello Mark, Thank you for your work on this [tremendous] problem [for us]. I am running the test on our 12 cores machine on the lab and so far so good [it did crash immediately when running the 'old' guile...] Not sure it interest you, but i made a module version of your test, where I also

bug#19770: goops - setter inheritance bug - serious

Hello, GNU Guile 2.0.11.114-649ec goops - setter inheritance bug severity - serious setters are beeing redefined, not inhereted: this is a serious bug. Cheers, David --8---cut here---start-8--- (define-module (a) #:use-module (oop

bug#20093: master: setting merge-generics duplicate-binding-handler @ expand time raises an error

Hello guilers, Hi Andy, Following our brief chat on irc, yesterday, here is he bug I was referring to: GNU Guile 2.1.0.322-eb3d6 setting merge-generics duplicate-binding-handler @ expand time raises an error. a) here is a short test case: --8---cut

bug#19459: #:export does not honor the merge-generics contract

> > Hi Andy, > > > >> > (define-module (a) > >> > #:use-module (oop goops) > >> > #:export ( > >> > !width > >> > get-width > >> > set-width)) > > > >> Here you export four bindings: one class and three generics. Those > >> three generics have methods on . > > > >>

bug#19459: #:export does not honor the merge-generics contract

Hi Andy, > > (define-module (a) > > #:use-module (oop goops) > > #:export ( > > !width > > get-width > > set-width)) > Here you export four bindings: one class and three generics. Those > three generics have methods on . > > (define-module (b) > > #:use-module

bug#20423: goops - inheritance of slot options

Hi Andy, > For what it's worth this is a part of GOOPS's design AFAIU: all slot > definitions are unique. Two slots named S declared on classes A and B > are distinct, even if A is a superclass of B. Well, as I explained in the original report, the only specification we have is CLOS: Stklos,

bug#19459: #:export does not honor the merge-generics contract

Hello Andy, > >> However... I believe merge-generics is intended to merge duplicate > >> imported bindings. It does not provide a copy-on-write version of an > >> imported generic, if that generic was not duplicated in the imports. > >> There is no facility in GOOPS to do that, AFAIU. > > It

bug#23243: ERROR: In procedure mkdir: File exists

Hello Damien, > When performing either a 'make check' or a 'make install check', a bug > occurs. The > following messages are displayed in the shell: > ... I am not a guile maintainer, but your message did trigger a ' bell':

bug#20093: Fw: bug#20093: master: setting merge-generics duplicate-binding-handler @ expand time raises an error

Hi again :) > ... > this works fine: I realized just after I sent that the compile-me script was not the latest version: no big deal, just this displays exactly what I pasted in the previous mail Here it is: ;; compile-me script starts here #! /bin/sh # -*- mode: scheme; coding: utf-8 -*- exec

bug#20093: Fw: bug#20093: master: setting merge-generics duplicate-binding-handler @ expand time raises an error

Hi Andy, > > This is a big problem for me, so I partially locally reverted that part of > > the patch, plus, I patch guild so it does this before anything else: > > (eval-when (expand load eval) > > (use-modules (oop goops)) > > (default-duplicate-binding-handler > >

bug#20423: goops - inheritance of slot options

Hi Andy, > > It actually is my intention, it has been for years, to study, dig into and > > work > > on our GOOPS implementation and start to help maintain it ... if I only had > > more > > time, I would have done it already. > > Till then we rely on you > I don't have any time to devote to

bug#20093: master: setting merge-generics duplicate-binding-handler @ expand time raises an error

Hello Andy, Further to the previous answer [of July the 2th 2016] > ... > But, you say, I only specified the duplicates handler after loading > goops! Well indeed, but if a module didn't specify #:duplicates, its > duplicates handling was implicitly dynamically scoped to whatever the > current

bug#20093: Fw: bug#20093: master: setting merge-generics duplicate-binding-handler @ expand time raises an error

Hi Andy, It is only after I answered that I did spot in the close associated with this bug report that we should 'get further detail' answering the bug id and not bug-id-done, hence this 'forward' > This was interesting -- turned out that GOOPS imports `map' from (srfi >

bug#24286: Guile-2.2: srfi-1 + #:duplicates (merge-generics...) + for-each raises an exception

Hello Guilers, Hi Andy, Here below a mini module [1], which raises an exception [2] using 2.1.3.104-8f2f8 (it compiles fine using 2.0.12). It looks a bit of a 'silly' module but the real one here do need this combination, I just minimized it for tracking purposes... For info, if I either

bug#27766: Bug with Guile 2.0.22

> But anyway, I suggest you report this to the MIT Photonics bandgap > maintainers, > because (a) there is no specific guile version checked at configure time, and > the > manual states what guile version is expected... correction: ... their manual _does not_ state what guile version

bug#27766: Bug with Guile 2.0.22

Hi David, > For my study, I try to use a simulation software named “ MIT Photonics > bandgap “. > This software uses the guile library for part of its calculation. > David$ mpb > Backtrace: > In ice-9/boot-9.scm: > 160: 11 Exception thrown while printing backtrace: > ERROR: In procedure

bug#28837: Guile 2.2.2: Loading srfi-1 with merge-generics breaks "map"

Hi Andrew, > (define-module (mytest f) > #:use-module (oop goops) > #:use-module (srfi srfi-1) > #:duplicates (merge-generics)) You need at least #:duplicates (merge-generics replace) but as I recommended in an earlier message, you should extend the default set

bug#29684: exception printers - request for improvement

... Thanks, David From 772cc05b1fe481a43be4c17c90ed3788cf37d2a6 Mon Sep 17 00:00:00 2001 From: David Pirotte <da...@altosw.be> Date: Wed, 13 Dec 2017 00:43:30 -0200 Subject: [PATCH 2/2] Allowing exception printers user customization * module/ice-9/boot-9.scm (exception-format, dispatch-exc

bug#29669: repl-print - requet for iprovement

From d920d22efe3e77d23004122e21cec420c402f531 Mon Sep 17 00:00:00 2001 From: David Pirotte <da...@altosw.be> Date: Mon, 11 Dec 2017 21:28:24 -0200 Subject: [PATCH] Updating repl-print to use truncated-print * module/system/repl/common.scm (repl-print): Use (truncated-print val), not (wri

bug#29684: exception printers - request for improvement

Hello Ludovic, > ... > It seems to me that you can achieve similar effect, at least in some > cases, by parameterizing ‘current-error-port’. It also makes more sense > to me to parameterize ‘current-error-port’ rather than set > ‘exception-format’, because the ‘exception-format’ is very

bug#29669: repl-print - requet for iprovement

Hi Ludo, Andy, > > scheme@(guile-user)> ,use (ice-9 pretty-print) > > scheme@(guile-user)> ,o print (lambda (repl obj) (truncated-print obj) > > (newline)) > > scheme@(guile-user)> (iota 500) > > $20 = (0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 > > 26 27 > > # …) > > >

bug#29684: exception printers - request for improvement

Hi Thomas, > ... > Hm. Applying the peanut gallery factor to my opinion (roughly 10e-7), I tend > to > side with David's position: the default consumer of REPL's print is a human, > and > feeding him/her with huge binary things isn't "tasty"... > But... grain of salt, and things. What would be

bug#15221: reiterating the request

Hello Tom, Mark, > You can enable it by adding the following two lines to your ~/.guile: > > (use-modules (ice-9 readline)) > (activate-readline) > > See . > I'm sympathetic to the desire to enable it by default ... We

bug#29684: exception printers - request for improvement

Hi Ludovic, > > It is perfectly fine, on the opposite side, to ask advanced scheme users > > (who > > would want to, but I really don't see the point) configure guile s the repl > > and > > the exception printer so it tries to print the full content of huge lsts, > > vectors, arrays ... >

bug#29226: fresh-auto-compile doesn’t invalidate the compilation cache

Hello Andy, Ludovic, Mark, > >> So I guess we should revert 83d4c4d622b406ec0bc9d8139ec8182fa72b5720 and > >> release 2.2.4 afterwards. Does that make sense, Andy? I hope (one of) you will find some time to look at bug#29669: repl-print - requet for improvement bug#29684:

bug#33305: Guile's Autoconf macros play not well with make distcheck

Hello Mark, disclaimer: I'm not a Guile maintainer, just giving you my personal opinion here > Consider an Autotools project that eventually wants to install some Guile > modules in the system. The canonical way to do this seems to add > GUILE_SITE_DIR to ... > However, this

bug#33305: Guile's Autoconf macros play not well with make distcheck

> ... > There are solution though, here is an example of what I do [1]. Actually, I do this for all the projects maintain, and explain all this in detail on the Guile-CV install page: https://www.gnu.org/software/guile-cv/install.html [ see "Install from ..." and following

bug#34185: GOOPS - metaclass with extra-slots made trying to define a getter, a setter or an accessor will raise an exception

Hello, Using a metaclass that defines extra-slots, will only work if the extra-slots are made 'exclusively' using the expression: (make #:name name) If one tries to pass a setter, a getter or an accessor, it raises an exception. Attached a code snipset to reproduce the error: drop it

bug#36251: Regex library doesn't recognize ']' in a character class

Hello, > ... > It turns out that there are several flavors of regular expressions in > common use, with different features and syntax. The link you provided > is using PCRE (PHP) regular expressions (see the "flavor" pane on the > left), and there are three other supported flavors on that web

bug#37066: Using GOOPS #:allocation #:virtual slot option causes stack overflow

Hello Jan, > I've written the program attached below and it hangs at writing > "after changing (K): ", computer freezes for a moment and then Guile > throws the following message: > allocate_stack failed: Can't allocate memory > Warning: Unwind-only `stack-overflow' exception; skipping

bug#36677: [PATCH] Don't truncate backtraces

Hello Mark, > > This change was prompted by recent discussion on the Guix lists: > > https://lists.gnu.org/archive/html/guix-devel/2019-07/msg00207.html > > In Guix, the truncation of stack traces frequently obscures > > important information due to the long filenames. > I'm sympathetic to

bug#36677: [PATCH] Don't truncate backtraces

Hi Mark, > You can see now that there are pressures coming from both directions > on this issue. I always 'did see' that, my point is that enabling truncated printing should be the default, and that we should be able to 'toggle' that to full printing anytime ... for the repl, errors, and

bug#47084: Guile 3.0 - The module-use! 'target' functionality is broken

Hello, > ... > (define-module (a) > #:use-module (srfi srfi-1)) > (eval-when (expand load eval) > (module-use! (module-public-interface (current-module)) >(resolve-interface '(srfi srfi-1 > ... Commit 19f38a38fde7da5fbcf29d0ebc4574e993210110 fixes the bug, many thanks.

bug#47084: Guile 3.0 - The module-use! 'target' functionality is broken

Hello, > ... > Commit 19f38a38fde7da5fbcf29d0ebc4574e993210110 fixes the > bug, many thanks. > Now, I have a question related to 'new' warnings though - I say 'new' > because there are no warnings in 2.2 - for which I don't see how one > can resolve those, unless mute them all by calling >

bug#47084: Guile 3.0 - The module-use! 'target' functionality is broken

Hello, Guile 3.0 The module-use! 'target' functionality is broken The code of module-use! itself didn't change, and call(s) to the procedure work(s) fine, but the functionality it is supposed to provide is broken. To reproduce, save the following minimalist module somewhere: ;;

bug#57379: GUI toolkit for Guile 3.0?

Hello, > > ... I'm trying to at least prototype a GUI in the same way that > > in Python I can write "import gi" and proceed to create a GTK > > window, add buttons and menubars and toolbars, etc. You might also try G-Golf - disclaimer, I am the G-Golf maintainer, I was hoping/waiting that some

bug#57379: GUI toolkit for Guile 3.0?

Hello Lee, > Thanks again, David. Welcome. > I was able to use a solution from Ricardo to get guile-gi to run > under guix I hope Ricardo, possibly with the help of other guix contributor's will find a solution so that g-golf may also run 'out of the box' on guix. > guile 3.0.7, which I hope

bug#57379: GUI toolkit for Guile 3.0?

Hello again > I sincerely apologize for opening a bug on the original issue; No problem. > It's not obvious to me how I can close this bug report. I'll close the bug don't worry. Cheers, David pgpGjmIfplwYv.pgp Description: OpenPGP digital signature

bug#57379: GUI toolkit for Guile 3.0?

Hello Lee, > I can confirm that disabling grafts allows both of the g-golf > examples to run, and they come up quickly. Great! > Thank you, Ricardo! 1+ David pgpfUl2Sfufoc.pgp Description: OpenPGP digital signature

bug#57379: GUI toolkit for Guile 3.0?

Hello Lee, > David, I was able to install G-Golf via guix, and that also worked > with the "use-modules" portion of your "Hello, World!" example. > HOWEVER (alas), both examples fail on the "use-typelibs" line, with: > Typelib file for namespace 'Gtk', version '4.0' not found This is a guix

bug#57379: GUI toolkit for Guile 3.0?

Hello Lee, > Thank you greatly, David. I cleaned up my guix environment and > reinstalled G-Golf, and now the hello world script runs but hangs > after these errors: > (g-golf-hello-world.scm:494347): GLib-GObject-WARNING **: > 12:37:46.818: cannot register existing type 'GdkPixbuf' This is a

bug#57379: GUI toolkit for Guile 3.0?

Hello Ricardo, Thanks for your help on this guix problem - G-Golf works perfectly fine on Debian - See the first part of my answer to Lee's message, the one that comments the GdkPixbuf bug that happens (only) on guix. > My first guess was that perhaps it gets confused because GTK 3 stuff > also