freenode/#lisp - IRC Chatlog
Search
17:44:06
warweasle
I'm pretty sure our highest language in 30 years will involve grunting like cavemen.
17:44:08
aoeu256
Yeah, but before we get to English well get to something half-way between Lisp and English, and it'd be nice to program in that.
17:47:06
warweasle
We need a way to speak lisp natively. I'm tired of translating ideas from english to lisp.
17:49:23
aoeu256
Hmm infix would be nice in the repl, and then change the infix to lisp especially with pipes(|>).
17:51:22
aoeu256
but sometimes its easier to type something when you can reorder the expressions anyway you want
17:53:24
aoeu256
Like lets say your writing code and you forget you needed a let, but your inside the expression. How do you write the let on the outside?
17:58:37
aoeu256
like lets say you are writing EXPR| and then you figure out you wanted (let (blah) EXPR|) where | is the cursor, or any thing else.
17:59:50
ck_
you type C-M-u to go up the syntax tree, then M-( to wrap the expression in parentheses, then type let ((var binding)...)
18:03:41
ck_
that gives you commands like redshank-letify-form-up and other more composite editing verbs
18:48:30
Josh_2
if I have two strings "a" and "1" how can I tell that one can be passed to (parse-integer ..) and the other cant?
18:49:09
Josh_2
I can obviously just catch the condition when I eval (parse-integer "a") and then do something, but I am curious if there is another way
19:27:48
pjb
edgar-rft: *print-radix* doesn't matter. if *read-base* = 2, then 2 is read as a symbol.
19:51:21
pjb
edgar-rft: perhaps, but since we cannot use base 0 to have 0 and 1 read as a symbols too, we'd have to use a reader macro anyways.
19:52:18
aeth
oh, that's fun. of course 'a is 10 when *read-base* is 16 and of course '9 is |9| when *read-base* is 8.
19:53:49
aeth
Now, when you match *print-base* with the *read-base* to, say, 8... well, now *print-base* and *read-base* are both 10 and '9 is 9, not |9| haha
19:58:02
pjb
You want to write your integers with a decimal dot to ensure base ten: (setf *read-base* 7) (setf *read-base* 16) (print (list 'a 'e '9)) (setf *read-base* 16.) (list 'a 'e '9) prints: (10 e 9) returns: (10 14 9)
19:58:55
pjb
Imagine the fun you could have, by messing with *print-base* and *read-base* in a few reader macros…
20:02:52
aeth
pjb: Imagine the fun you could have by SETFing *print-base* and *read-base* in a basic dependency that's loaded early on by ASDF, such as in Alexandria!
21:54:52
sahara3
p, li { white-space: pre-wrap; } Anuel AA, Daddy Yankee, Karol G, Ozuna & J Balvin - China
22:20:45
aeth
Not one line about Lisp or Common Lisp. I wonder how they found this place, and if they had a Lisp question and were just waiting to ask or if they thought this was some general chat room.
23:04:44
alexanderbarbosa
someone just rated a book 1 star because the code from a example did not look a perfect "circle"... lol
23:10:51
aeth
alexanderbarbosa: I rate everything that claims to produce a circle 1 star because I have yet to see a perfect circle
3:39:34
dtornabene
hey, I'll try in here, see if anyone bites: has anyone actually used the guile scripting extension for GDB, or know of publicly available code I could read that does so?
3:40:46
beach
Since this channel is dedicated to Common Lisp, you may not get any good answers to that question.
3:41:08
no-defun-allowed
Well, most #lisp readers are familiar with Common Lisp and not so much Guile. Maybe there is a #guile that would have better knowledge?
3:48:27
dtornabene
I knew it was CL focused, I just figured there might have been enough overlap in users that someone might have seen it, sorry for the noise!
3:49:42
dtornabene
its just kind of got me spooked (in terms of ease of use) GDB has provided a guile api for five years now .....and theres no code that I can find in the wild. weird!
3:53:25
vsync
oh hum.... *read-base* and friends; is there a handy thing to bind or set all reading variables?
4:01:42
remexre
weirdness: https://azeban.remexre.xyz/screenshots/f7fefd9169f89fa468ab791897d6e25c6052dc66.png
4:04:40
remexre
I'm using (make-array 0 :adjustable t :element-type 'character :fill-pointer 0) to create it, and (vector-push-extend)-ing into it
4:34:34
vsync
no-defun-allowed: I guess to whatever their defaults are specified to be... do they all have defaults?
4:35:56
vsync
perhaps I'll make a with-safe-io-syntax that starts with that but sets *read-eval* to nil etc