freenode/#lisp - IRC Chatlog
Search
9:55:08
contrapunctus
phoe, beach, flip214: do y'all need something like this? https://github.com/CommonDoc/scriba
9:56:54
jackdaniel
contrapunctus: the point is to have a "live" documentation in a program (in contrast to a source code), with ability to save/restore that documentation
9:57:36
jackdaniel
then you can add import/export functionalities, or even live markup parsers when writing the documentation
10:08:02
contrapunctus
Well lol "This library can be considered an implementation of Robert Strandh's suggestion for the creation of a library for representing documents [...]"
10:28:55
splittist
I think most document modelling goes too quickly from the abstract (tree) to the particular (italics, numbered list). There are useful layers that could fit in between.
12:48:02
beach
phoe: Heh, so it's good to see that someone is paying attention (referring to commondoc).
17:32:16
jackdaniel
by standard he meant something what is /expected/ to be implemented by common lisp vendors
17:54:53
_death
so, where's the spec? it's just a library that people use.. there are others like it.. and now it'll be two libraries in one
17:59:23
Bike
i also meant something that's more exacting about specifications than portability libraries usually are
18:00:01
Bike
something that's important with atomics because debugging problems related to them is really annoying.
18:01:29
aeth
debugging problems related to threads is really annoying, atomics are just unnecessary in single-threaded programs.
18:02:13
Bike
i meant atomics makes things even worse than normal multithreaded programs. I thought that was obvious.
18:02:31
_death
it seems the new interface will have a document associated with it, but it's in a very early state.. https://sionescu.github.io/bordeaux-threads/
18:04:00
Bike
that's pretty reasonable in light of how patchy things are across implementations per shinmera's tracker
18:06:44
Bike
yeah. i've thought some about what an actual standard would look like and it would at least require a fair bit of work on every implementation
18:08:40
fe[nl]ix
for example, some implementations support atomic ops for struct accessors, but only for boxed slots
18:09:22
Bike
and one of the few libraries i could find using atomics, lparallel, assumes reads are sequentially consistent, i believe
18:10:49
fe[nl]ix
the only implementation that has a documented and well-thought API for barriers seems to be Lispworks
18:28:24
jackdaniel
timeouts are not implemented (I have them working locally, but that needs cleanup I did not have time to apply lately). also, they are based on spinlocks for portability; I suppose using i.e pthreads unices would be better for both cpu and performance
18:28:57
jackdaniel
I want to also bring back green threads, so there is n-to-m mapping; but that's another story
18:39:26
fe[nl]ix
jackdaniel: once Linux gets support for usermode scheduling, I'd like to experiment with a simpler Lisp before adding that support to SBCL
18:42:44
p_l
fe[nl]ix: doesn't read to me as full MxN threading... more like another implementation of what was part of QNX RPC port or the code that is part of Android Binder
18:45:01
jackdaniel
fe[nl]ix: if you have questions regarding ecl (if you decide to experiment with it) please let me know
18:55:40
fe[nl]ix
it's technically still 1:1 but the process can determine its scheduling priorities and control switching
19:04:02
p_l
Binder did that combined with the RPC - this meant that when you call a "remote" service, you stay in the same scheduler time slice
19:36:26
Duuqnd
From usocket's page on common-lisp.net: "(IPv6 support is also in progress and already available for SBCL/CCL with version 0.6.3+)"
19:37:36
gendl
now i have to make sure i have that version and see how to use it. I'm not seeing an argument for ip version in usocket:socket-listen
19:45:21
gendl
yeah i'm not seeing anything about ipv6 in https://common-lisp.net/project/usocket/api-docs.shtml
19:57:39
gendl
if you simply specify an ipv6 host to socket-listen, it'll be a ipv6 socket. Or just use *wildcard-host* which will make it listen for ipv6 connections on ipv6 capable systems.
20:06:45
phoe
I remember being stung by usocket that making a socket on "localhost" opened a socket on ::1
20:44:39
MichaelRaskin
Ah right, ::1 for localhost. I wonder when it will listen both protocols on loopback. like :: includes listening on 0.0.0.0 in some casesā¦
21:08:28
jcowan
What are use cases for conditions that are neither errors nor warnings? (I know that storage-condition is neither.)
21:11:22
p_l
also, the classic example is about interactive REPL, I believe, where technically there's an error
21:11:47
jcowan
That sounds more like restarts than conditions. What I am asking is about application condition types that descend neither from `error` nor from `warning`.
21:19:20
lonjil
jcowan: all condition handlers can do non-local control flow, and in any case you'd would signal a condition for someone to be able to select a restart even if there's no error or anything to warn about.