freenode/#lisp - IRC Chatlog
Search
0:18:28
pillton
jasom: Specialization-store can inline calls to "methods" if there is sufficient type information available.
0:19:59
pillton
jasom: https://github.com/markcox80/specialization-store/wiki/Tutorial-3:-Compile-Time-Support
1:27:57
jasom
anyone know if cl-sqlite is still being developed, and if so, where to report bugs? The mailing-list link on the webpage is broken...
2:53:06
myrkraverk
My very first asdf system has a name conflict whenever I re-compile it, when I load it with (ql:quickload) however, on subsequent loads, it succeeds.
2:54:23
myrkraverk
That is, I have a name conflict in :common-lisp-user and :my-package when I load it with (ql:quickload :my-package) and it needs to compile source file again.
3:34:56
Fare
asarch, he hasn't been in #lisp in many years. Not sure he uses it much if at all these days.
4:08:29
asarch
A book that you can use as a reference manual (how to open files, how to list directories, etc)
4:09:35
aeth
PCL is more of an introduction. Common Lisp Recipes (same publisher, different author) is more of a reference. I don't think it's online. The ebook was on sale for $10 on Black Friday. So... you'd have to wait almost a year
4:16:50
aeth
The core language features of Common Lisp haven't been changed in over two decades. The language extensions are a mix between just as old as the language (things that didn't get in the standard, but could have) and fairly new things. They still move fairly slowly. But everything else is just like any other programming language, and it changes over time.
4:50:09
pierpa
The best reference manual for CL is CLTLII + checking CLHS to be sure particular things haven't changed.
6:04:52
asarch
One stupid question: I start sblc and then type a few expressions, is it possible to save them into a file?
6:19:12
myrkraverk
For example I have it configured with :history #p"~/.sbcl.history" ; in my .sbclrc
7:17:17
smokeink
Is there any easy/idiomatic way to find all symbols that are fbound to some function ?
7:29:19
loke
Does anyone know of a nice library that can parse infix expressions as strings and evaluate them?
7:32:12
myrkraverk
It's basically the tutorial in most compiler books, but I don't know about a library for it.
7:33:28
myrkraverk
As in, flag1 flag2 flag3 are meant to be mutually exclusive and so far, each is a simple parameter.
7:33:48
myrkraverk
For two, I can just use (and flag1 flag2) but it gets harder when there are 3 or more.
7:35:19
myrkraverk
Of course there's something simple to do it. I was thinking about rolling my own with LOOP.
7:35:56
loke
If you have lots of flags, LOOP witll be more efficient as it will allow you to exit early.
10:19:18
specbot
Processing of Top Level Forms: http://www.lispworks.com/reference/HyperSpec/Body/03_bca.htm
11:22:22
jmercouris
every letter is a symbol, and together they compose words which are also symbols which ultimately express something
11:36:03
pjb
jmercouris: I would argue the symbolic expression is more precise, by being more fuzzy on the actual ranges of frequency, and also, ontologically, since an actual perceived color (light frequency) can be different from the actual color of the surface, under light conditions.
11:36:44
Zhivago
It's not a very interesting grammar -- just one composed of atoms and forms, where a form is a list of atoms or forms.
11:38:30
jackdaniel
my point is exactly that – are shorthands for forms also considered s-expressions?
11:39:25
pjb
jackdaniel: now you always have the ambiguity between the textual form and the read form. But formally you can accept the textual form under those definitions.
11:40:55
Zhivago
Fortunately, reader macros aren't part of the definition of symbolic expressions, so we can exclude those.
11:42:45
pjb
the usual definition of sexp := atom | ( sexp… ) . wouldn't take into account circular structures.
11:43:46
kolb
the current onslaught of "let me document all your projects using my $docgenerator" has to stop -.-
11:44:50
kolb
No I have two zombie sites that *mis*-render the polished docs of my projects without me ever having opted in to that, and seemlingly no way to make them *stop*.
11:44:59
Zhivago
Just go back to the Recursive Functions of Symbolic Expressions and their Computation by Machine paper. :)
11:45:54
kolb
quickdocs and quickref are imho the CL equivalent of yellow-pages sites that come up when you google for something. It’s *never* the site you are looking for. They are content mills.
11:47:39
kolb
Zhivago: to whom? quickdocs is unmaintained and just a ghost ship floating the S3, quickref probably has way other priorities than me and my polished docs, and was done in an internship
11:48:33
kolb
There is no editor, that’s the whole point. These projects just blindly scrape quicklisp and dump the result on the net.
11:51:57
Zhivago
kolb: Do you want to do a better job, or just not see those results in google searches?
11:52:28
Fare
kolb: I'm sure Didier Verna, who oversaw quickref, will be glad to accommodate your requests for an API to customize how quickref extracts documentation for you.
11:55:23
kolb
Zhivago: I want the announcement of $docportal to include a reasoning of 1) why its supposed to supersede existing broken $docportal, 2) how they deal with the natural issue that there is no defined grammar for docstrings, 3) document a way to opt-in/out (the "I scrape facebook and host profiles" model is not new, and neither are the issues with it)
11:55:41
kolb
Sorry for ranting guys. Obviously I will not write a stern, but friendly letter, detailing my issues.
11:56:16
Xach
I think the projects are done in good faith to improve the experience of people trying to find and use documentation. I think shortcomings are worth discussing.
11:57:48
Zhivago
Perhaps what you rally want is a link from the documentatoin on those sites back to your site?
11:58:11
Xach
kolb: The way you describe the effort makes it sound maliciously lazy and incompetent.
11:59:11
kolb
Xach: it is objectively neglecting, since these projects expect the content providers to run after the content farm owners to fix issues.
11:59:24
jmercouris
pjb: symbol: a mark or character used as a conventional representation of an object
11:59:35
Xach
I've found quickdocs pretty helpful in the past. I was under the impression it was actively maintained.
11:59:46
Fare
kolb: if you provide a declarative way to specify what documentation convention a given system uses, you can help solve the issue.
11:59:46
jmercouris
I don't mean symbol as in the common lisp usage of symbol, but the generic definition of symbol
11:59:56
Xach
It's nice to search for e.g. "decode base64" and get a handful of potentially useful results in a single place.
12:00:00
jmercouris
unless of course we say that within S-exp, we define symbol to have a meaning specific to the context of common lisp
12:00:28
jmercouris
Zhivago: Outside of the context of common lisp exists a definition of symbol, that's the one I'm using
12:01:40
kolb
I don’t want to take quickdocs/quickref from you guys. I just don’t want my polished documentation to be mangled by it. I put a lot of work into hosting and working on my docs. And when people find them on quick$foo instead of my site, they will think its broken.
12:03:42
kolb
Xach: my problem is not with the concept, my problem is that its auto-opt-in and now I am forced to run after two projects to fix things. I.e. work out of nowhere.
12:04:20
Zhivago
jmercouris: Why are you talking about s-exps in terms of symbols rather than atoms?
12:04:45
jmercouris
Zhivago: I'm just taking the name "Symbolic Expression" and saying that all expressions that are communication involve symbols