freenode/lisp - IRC Chatlog
Search
6:42:25
fiddlerwoaroof
I'm not entirely a fan of its style, but the way it uses the language is fairly different from how I use it
7:13:34
fouric
i've read through the chapter at least twice, but wasn't able to parse it very well, unfortunately
8:32:17
mfiano
Is there anything that can help me to check that a form is in the correct shape, so I can emit a meaningful error message for the user in the DSL I am writing, before parsing it with destructuring-bind giving them a bad error?
8:33:15
beach
In general, you would have to write a parser for it, using one of the parser-generator libraries.
8:35:46
mfiano
The form is quite simple. I should just manually parse it. It looks like '(some-symbol (&key &allow-other-keys) &key &allow-other-keys)
8:38:47
verisimilitude
If you don't care to write a great error message and depending on what the expansion is, you could always just write it so rule violations cause the expansion to fail in compilation; this is what I like to do.
10:57:54
schweers
Depending on the order in which I have my test cases, one branch or the other is claimed to be taken only one way. So some data seems to be lost?
11:00:29
schweers
I’m off for lunch for now, so sorry for not following up on any answers which may come ;)
11:04:33
scymtym
schweers: are you looking at the coverage of the test code itself? some test frameworks compile the test code when running the tests instead of ahead of time
11:56:28
flip214
> pkhuong> | I should also commit my fix to make SB-COVER obey in-package roughly the same way as swank
11:57:05
schweers
I have no idea. I just stumbled upon the coverage tool a few days ago and really like it.
12:04:19
loke
and there are about 300 billion different OBJ formats. :-) Which one are you thinking of?
12:05:06
flip214
loke: No, a 3D file format (from Stereolithography) -- nowadays used for 3D printing
12:12:05
flip214
where can I see what the source location of https://quickref.common-lisp.net/stl.html is?
15:30:33
akr
Hi, once I'm at a breakpoint in the debugger and I see the call stack, how do I examine the arguments with which a call in the stack was performed?
15:51:52
schweers
I wonder why people (myself included) find it harder to read all caps text than all lowercase text.
15:52:27
verisimilitude
I believe the explanation is we're more accustomed to lowercase and so better at recognizing it.
15:53:08
verisimilitude
That was my second guess. In any case, I can't link to the source, as I don't recall it.
15:53:27
sjl_
I like the all caps when looking at a repl session because it's easy to distinguish my input from the output. But it is pretty miserable to read large blocks of it like that.
15:54:27
verisimilitude
It makes for a nice delimiter for when I want to refer to Common Lisp. If I write in uppercase, it's rather easy to know which symbol I'm referring to.
15:56:40
verisimilitude
I recall being criticized for using it in my documentation, _death; I was told it belongs in the 1980s or something or another to that general effect.
16:01:06
_death
verisimilitude: don't take it too seriously.. opinions vary and there is an abundance of peanuts ;)
16:03:20
verisimilitude
Now since you're here, _death, I was wondering about that library you've been writing. What's the progress on that?
16:03:23
_death
verisimilitude: in general I wouldn't use &aux, because I don't think the lambda list is the right place for such variables.. but style flows and ebbs with years and programs..
16:07:36
_death
verisimilitude: well, I did touch it since our conversation, but mostly to pretty up some interfaces.. the pace for personal projects is the snail's..
16:09:01
_death
verisimilitude: sure.. in the meantime, it would be helpful to set up a git repository of your libraries though
16:10:36
verisimilitude
Well, I try to not release anything breaking. What did you have an issue with in particular?
16:11:16
verisimilitude
I've been trying to mostly add to ACUTE-TERMINAL-CONTROL, rather than change what's already there in a way that would break something.
16:11:55
_death
verisimilitude: I think you removed the mouse enable/disable function names from the export list
16:13:05
verisimilitude
Oh; I did do that, yes; I decided it wasn't reasonable to provide that. I generally try to avoid doing that, though.
16:16:28
_death
verisimilitude: I suggest to give it a try.. it's a complex tool but if you have the right model it's fairly simple to understand, and most of the time it's fairly simple to operate..
16:17:18
_death
verisimilitude: for a simple model, I think https://jwiegley.github.io/git-from-the-bottom-up/ was helpful
16:18:05
_death
verisimilitude: but for simple use, just create a directory, "git init", add some files, change them, and use "git-gui" to commit etc... and yes, magit is great too
16:19:51
verisimilitude
I've taken a quick look and everything currently in ACUTE-TERMINAL-CONTROL will stay, certainly. There's a PROPERTIES and (SETF PROPERTIES), but that's not documented because I'd like to have a better name and I'm not certain how I should best expose that, if at all.
16:20:28
verisimilitude
Considering these libraries are single files, I'd rather avoid this, _death, but I appreciate the advice in any case.
16:22:31
_death
verisimilitude: I'm guessing you associate version control with heavy set ups (servers, multiple authors) and this is why you wish to avoid it
16:23:21
verisimilitude
I'd rather avoid learning an explicit worse-is-better version of a decent file system.
16:25:30
verisimilitude
That's the gist of the present, I suppose. I know I should probably start doing something different.
16:26:00
verisimilitude
I've been told that my stuff is neat, but if I'm not on Github or some other big site it will mostly go ignored, and that's true, unfortunately.
16:26:06
_death
verisimilitude: just take an hour or so playing with chapter 1/2 of https://git-scm.com/book/en/v2
16:27:52
_death
verisimilitude: it's not necessary to use github, although it makes things simpler.. you can set up your own git serving daemon, or even a web front.. (you don't even need that; git can use http to clone a repository, but...) it's not a big deal
16:29:29
verisimilitude
Well, unlike everyone else who's told me to do this, you're actually using some of my software, so I'll consider it, _death.
16:30:30
_death
verisimilitude: sure.. maybe you'll find that it's very convenient (especially with magit...) to use git for any text that you happen to be editing
16:31:17
verisimilitude
As with most software, I'm going to want to use it as little as possible, _death.
16:31:24
schweers
git can even be useful locally, if you are the only person using it, and not sharing it across any machines.
16:34:47
verisimilitude
In any case, SHUT-IT-DOWN and CL-ECMA-48 are effectively finished and I could leave them as is, even though I'll occasionally make minor improvements, so I'd only be using git for ACUTE-TERMINAL-CONTROL if I decide to use git.