IRC channel logs

2019-11-26.log

back to list of logs

***daviid`` is now known as daviid
***apteryx_ is now known as apteryx
<zig>hello #guile
*RhodiumToad ponders whether using parameters is a good idea
<zig>RhodiumToad: what it is the context?
<RhodiumToad>wondering whether it would simplify a case that would otherwise require a bunch of optional arguments passed down through various functions
<RhodiumToad>the context is trying to do a better job of outputting xml with namespaces than SXML currently does
<zig>hmm idk
<zig>I just did some statistics about words used in bug-guix mailling list, and without surprise, the term 'ludovic' appears in the top: https://paste.gnome.org/po69flbyv
<wingo>moin
<wleslie>what's new, andy?
<zig>is it possible to pass -O3 to guile command? does it make sense?
<zig>also how to force the JIT to kick in?
<wingo>zig: -O3 is mostly used in "guild compile" currently
<wingo>civodul: for that crc32 bug -- it is on x86-64 ?
<wingo>ah i see it is a compiler bug, not a jit bug
<wingo>nice :)
<wingo>nice, nice
<wingo>fixed
<civodul>woow, that was fast :-)
<civodul>it was on x86_64
<civodul>i was happy the test was able to catch a real obscure bug
<chrislck>daviid: looking at guile-cv, was initially intrigued... but guile-cv suffers from 'gnu webpage syndrome'
<chrislck>good documentation and instructions, and not enough 'pop'
<chrislck>small snippets showing power of guile-cv, hiding just enough tech to whet appetite
<chrislck> https://www.gnu.org/software/guile/ is the level that we want to see
<chrislck>perhaps a minimal project description using raspberrypi's camera module, distro, guile, guile-cv, and catcam ;)
<zig>wingo: fwiw, an numerical-overflow error is raised when compiling the following program: https://paste.gnome.org/pextmlevy
<zig>the parens are not good, line 7 should be inside the "if".
<zig>another bug: when a file is already compiled, and the new compilation fails, guile will run the previously compiled file.
<dsmith-work>Tuesday Greetings, Guilers
<bandali>davexunit, hey are you around?
<manumanumanu>About Parameters: are they slow?
***ng0_ is now known as ng0
***jao- is now known as jao
<jcowan>manumanumanu: Binding them or reading them? Reading is a procedure call, so should be fast.
<jcowan>Depending on the implementation, forking a new thread when lots of parameters exist may be slow.
<daviid>chrislck: thanks for the nice words wrt guile-cv, are you 'from the domain'? you might be interested take to take look/use aiscm as well
<daviid>chrislck: I will get back to guile-cv as soon as g-golf is 'complete' ... there are tons of things to be done still ...
<daviid>chrislck: wrt its doc, I will only concentrate on the reference manual as I am developing, till guile-cv has what I consider a minimum functionality set (it still misses fundamental things, like watershed, fast fourier transforms ... and many many other fundamental bits), meanwhile, if a user wants to help and write 'pop' small snipsets :), I certainly can review and include some in the user part of the manual ... if you want to work on
<daviid>this, make sure the images are GPL licensed
<daviid>*the images you would use
<daviid>* there are tons of things to be done still on guile-cv, g-golf is getting close to be fully usable (though there will always be room for improvements, once 'complete', maintenance and enhancement will demand less effort then it is demanding now ...)
<daviid>chrislck: aiscm is here http://wedesoft.github.io/aiscm/
<ArneBab>chrislck: if you need free images, you can use those from the RPG I write: https://bitbucket.org/ArneBab/1w6/src/default/Quelldateien/
<daviid>chrislck: did you actually install and try guile-cv, or just looked at the online doc? just curious ...