freenode/#lisp - IRC Chatlog

6:50:47 beach` ** NICK beach

6:53:24 beach Good morning everyone!

6:57:26 edgar-rft The early bird catches the worm, what makes me think that morning is probably not so good if you're a worm.

7:00:32 jackdaniel there was a story about a frozen bird in this spirit, quick search in my favourite search engine which doesn't start with G gave me this reddit link: https://www.reddit.com/r/Jokes/comments/1j0h49/the_frozen_bird/ :)

9:43:50 enrio ** NICK iamnoob

9:44:00 iamnoob ** NICK iamnoobb

10:46:41 luis Has anyone implemented a compatibility library around excl:fwrap, sb-int:enscapsulate, etc?

11:03:42 Shinmera What does that do?

11:05:40 phoe https://github.com/sbcl/sbcl/blob/2603efb1b07513ade0a5fdbebf1a16bd923bc937/src/code/fdefinition.lisp?ts=8#L249

11:06:44 Shinmera What would you do with that? An attempt at a portable TRACE or something?

11:07:49 luis Yes, among other things.

11:08:50 luis It's useful for monkey patching, too. Not that I recommend monkey patching at home.

11:11:54 scymtym Shinmera: this hybrid (deterministic/statistical) profiler uses the encapsulation facility: https://techfak.de/~jmoringe/clamegraph-rewrite-1.ogv (the video doesn't reflect the current state but conveys the basic idea)

11:12:15 Shinmera nice

11:13:38 Shinmera luis: If you make a portability library, let me know so I can add it to the overview.

11:14:44 luis Aye.

11:21:54 luis SBCL doesn't support tracing flets and labels does it?

11:23:22 scymtym i think ENCAPSULATE would work with the function object, but there is no way to refer to local functions in TRACE

11:24:14 luis scymtym: is there a way to grab the local functions at all?

11:25:21 Shinmera how would you?

11:25:51 phoe upi

11:25:55 phoe I mean uhhh

11:26:26 phoe you'd need to crack the function object to get its references to local functions

11:26:49 Shinmera often the functions might not even be there at all

11:27:02 scymtym i thought something like (labels ((foo ())) (encapsulate #'foo)) could work but ENCAPSULATE seems to assume global functions

11:27:03 phoe e.g. inling and such

11:30:40 scymtym there is also ENCAPSULATE-FUNOBJ (added two weeks ago) which might work, but i haven't looked into it

11:37:24 luis phoe: FWIW, Allegro CL supports tracing labels/flet. It seems like it may be only one of the few Lisps that supports that.

11:41:49 p_l in compiled code as well?

11:47:58 phoe Has anyone succeeded running the modern ANSI-TEST on CCL?

11:49:09 phoe ...ooooh. I see now. OK - I've finally managed to run them.

11:50:57 luis p_l: yes.

13:04:57 lukego Hey is anyone else doing Lisp with Nix? I'm open to see tricks and snippets if anybody has them. I've found ql2nix and that seems to work pretty well for making a stable Lisp distro

13:07:05 Cymew What the heck is "nix"?

13:08:14 Bike https://nixos.org/

13:11:11 lukego Yeah, it's a package manager of sorts.

14:08:20 dale_ ** NICK dale

14:23:14 Xach lukego: a few people talk about it from time to time - MichaelRaskin for one, buffergn0me for two - a few others

14:36:43 p_l lukego: I know of people who gave Lisp as reasons for abandoning NixOS

14:36:59 Xach nooo

14:37:09 p_l in my practical experience it felt good as deployment target but development was often problematic, not just with lisp

15:22:34 phoe Hey #lisp - I would like a review for the Travis configuration that I have prepared for the CCL repository.

15:22:39 phoe https://github.com/phoe-trash/ccl/commit/efa46513e9a362a0bef8c47f3969d2948f86af04

15:23:16 phoe The Travis build that has just started for this commit is available at https://travis-ci.com/phoe-trash/ccl/builds/134026306

15:23:31 Cymew Very creative to implement your own distro since you were fed up with existing package managers.

15:23:50 phoe The build overall is supposed to fail, since ANSI-TEST and CCL-TESTS are currently failing.

15:24:03 phoe Cymew: smells like /xkcd standards

16:55:01 rumbler3113 alright lispers, coming at you with what is likely a noob question