freenode/#lisp - IRC Chatlog
Search
3:50:57
aeth
What should I call my library to turn a variant of markdown into html for my static site generation? I fully expect it to bloat over time to cover other A->B transformations so I don't want to give it a specific name.
3:52:59
aeth
White_Flame: the thing is, I might want ot have another source (even just another md flavor) or another destination (even just xhtml or xml)
3:55:43
aeth
and before you know it it's converting restructuredtext to org-mode because of how things just develop over time
4:14:38
jgodbout
call it md2html, either a) it'll limit the bloat as a mental note or b) YOLO and at least youll have the memories
5:23:55
edgar-rft
aeth: if you want to avoid a specific name, just call it unspecific. That would perfectly resemble the state of most markup languages.
5:26:27
lisbeths
If there is no flaw in the common lisp hyperspec then why does the military often choose ada instead?
5:33:53
pjb
lisbeths: there's a flaw in clhs: it specifies prog2 to return the result of the first expression.
5:34:25
beach
lisbeths: Second, where do you get the idea that the military would avoid choosing something just because its specification has flaws in it?
5:42:27
beach
lisbeths: yes, but there is no reason to believe that the Ada specification is less flawed than the Common Lisp HyperSpec, nor, as I pointed out, that the military avoided Common Lisp just because the Common Lisp HyperSpec has flaws. You just don't have any basis for that.
5:42:40
pjb
lisbeths: furthermore, there's no formal specification of CL. This would have to be redhibitory for the DOD, if I was the DOD… https://dl.acm.org/citation.cfm?id=800054.802002
5:43:12
lisbeths
Why would the DoD choose ada if they could prove that neither was more flawed than the other?
5:44:02
beach
lisbeths: Notice that we are talking about the Common Lisp HyperSpec, i.e. the document. Not the language as it was intended, despite the flaws in the specification.
5:44:40
lisbeths
Why would the DoD exclude languages written to the specification of common lisp and choose ada instead?
5:45:15
beach
lisbeths: Furthermore, you started by assuming that the Common Lisp HyperSpec has no flaws, but we already told you that it does, so what is your point?
5:45:21
pjb
lisbeths: because an implementation written to the specification would do: (prog2 1 2 3) -> 1
5:46:41
beach
lisbeths: It appears that you have no insight into the process used by the military for choosing, or not choosing, specific languages. There is no reason to believe it has to do only with flaws in the specification. If you think otherwise, please provide some evidence for that.
5:47:52
Jachy
lisbeths: here's the answer http://home.pipeline.com/~hbaker1/sigplannotices/gigo-1997-04.html
5:48:10
pjb
lisbeths: why don't you just ask them directly? Public Communications - DOD Public Affairs / 1400 Defense Pentagon / Washington, DC 20301-1400
5:53:28
no-defun-allowed
lisbeth: I wouldn't expect any sense of sanity or reasoning from military officials, honestly.
5:55:05
no-defun-allowed
As in, a mathematical model for the language. I started reading the one for Standard ML on the weekend, then gave up since I'm not good with mathematical notation.
5:57:42
semz
Seems excessive to make that a requirement, even though it's useful. Then again I'm not running the shop
6:03:16
lisbeths
It basically said. "Communist bad. Trick communists into using software we know is bad and we'll use it too but we'll use the bad software better."
6:03:50
lisbeths
If someone believed that document 100% they would come to the conclusion that the military preferred certain other languages to the ones they chose.
6:06:26
no-defun-allowed
sounds like an April Fools' document to me, but I would also expect that kind of stupidity to come out of a red scared US government
6:08:17
lisbeths
Another hard to believe thing is that the americans could actually decieve the russians into using worse software.
6:15:52
alandipert
p_l nevermind about let not interning binding syms - they're definitely interned. my arg to find-symbol just wasn't uppercase
6:16:07
lisbeths
I argue this channel has no topic and if you say that there is try to talk about that topic for a prolonged period of time to test that is indeed the topic. I ague you will find that any topic that is listed will not be satisfactory.
6:18:23
beach
SaganMan: Steady but slow progress. I am working on translating high-level intermediate representation (HIR) to medium-level intermediate representation (MIR) for SICL.
6:18:58
beach
Luckily, there are now many people helping out with SICL and other essential projects.
6:19:59
beach
Heisig is working directly on SICL. And Bike continues the work on Cleavir. Many people, including jackdaniel, loke, scymtym and others are doing fantastic work on McCLIM
6:20:55
beach
Heisig is also working on Trucler, a modern version of the CLtL2 environment protocol.
6:21:30
beach
And scymtym is working on several things, including a better inspector (Clouseau), the Eclector reader, and many libraries that will turn out to be highly useful in the long run.
6:46:53
SaganMan
beach: I don't get enough time to do programming. I code lisp some time ago, did project euler problems. Upto 50 problems.
6:50:29
beach
If I am counting right, it has resulted in 13 ILC or ELS articles since 2014. So it is not just code, but also new techniques and such.
8:14:17
beach
GAH! Four hours spent on proofreading the next chapter of Dyomkin's book. But I think it is a very important document, so I consider it part of my job description to do it.
8:36:20
ck_
That's a good thing too. Too many errata are too long because .. well I can only speculate. Editors place too much faith in the authors? Publishers in the editors? and so on
9:42:23
beach
flip214: That's OK, I'll do it. But another pair of eyes might be appreciated. There are already a few chapters on planet.lisp.org and I think they are still possible to update.
9:43:35
flip214
beach: ack, will try to. so, basically http://lisp-univ-etc.blogspot.com/search/label/lisp, right?
13:29:12
jonatack
beach: good that you are doing it. Dyomkin's content is very good and interesting but the writing does need proofreading. hope he is using it.
13:40:42
Josh_2
what variables do I need to initialize in my top-level function when I save-lisp-and-die?
13:42:56
pjb
Also, variables that reference values that will be different when you ressucitate your lisp image.
13:43:50
pjb
Josh_2: this doesn't mean anything: there can be compilation-time configuration files, and run-time configuration files.
13:45:07
pjb
So the point is to initialize the variable at the time they need to be initialized, with the correct values for that time.
13:46:01
pjb
Josh_2: why do you keep giving irrelevant facts? Being the first file mentionned in a system definition file means nothing.
13:47:24
pjb
Also, it would be a good idea to keep the configuration in a single object or structure…
13:47:50
pjb
It's better to limit the number of global variables, the more so when they are special.
13:48:34
jmercouris
I disagree about limiting the number of global variables, I think that strongly depends on the application
13:49:41
pjb
jmercouris: also be sure to have several variable with the same symbol name in different packages…
13:52:04
p_l
pjb: global variables are common way to implement forms of pub/sub messaging in realtime systems
14:14:11
jmercouris
Xach: did you use any documentation to learn about them, or just look at the source or?
14:14:39
Xach
jmercouris: I had a fairly firm basis of understanding of the underlying Unix API, and the sbcl interface is a very thin layer.
14:15:51
Xach
jmercouris: I don't know how well that would work. section 7 of the unix manual for ip, tcp, and udp could help. as well as IPC chapters of unix books.
14:16:23
jackdaniel
if you want to get a basic communication working take a look at dependents.lisp file in clx
14:18:08
jmercouris
jackdaniel: I only see a dependent.cl file here in https://github.com/franzinc/clx
14:18:22
Xach
unix network programming by stevens helped me back in the day. things have changed a lot with regard to new ways to multiplex and stuff but the fundamentals still work.
14:20:06
jackdaniel
basically you want: (make-instance 'sb-bsd-sockets:local-socket :type :stream) (sb-bsd-sockets:socket-connect * "/foo/bar") (sb-bsd-sockets:socket-make-stream ** :element-type '(unsigned-byte 8) :input t :output t :buffering :none)
14:20:24
jackdaniel
where stars are limited to count of two to avoid being accused of being a three-star-programmer
14:28:51
Xach
I don't particularly like SBCL's socket API, but the good news is that it takes only a small amount of code to make a new API with sb-alien if you like.
14:37:30
Xach
jmercouris: the code of sb-bsd-sockets is relatively small and it uses ffi to do its work.
14:37:48
Xach
jmercouris: if you don't like what it presents, you can make something that you like better without much work.
14:39:37
Xach
In my experience, it was about as easy to add the FFI interface I liked as to build an interface I liked on top of one I didn't like.