danieli has quit [Read error: Connection reset by peer]
donleo has joined #commonlisp
danieli has joined #commonlisp
rtypo has quit [Ping timeout: 245 seconds]
wacki has joined #commonlisp
char has quit [Remote host closed the connection]
<beach>
I haven't read it, but it looks interesting. I am guessing that it doesn't use Common Lisp as defined by the standard, because of the publishing date, put perhaps it uses CLtL1 Common Lisp.
<beach>
I would like to see a free grammar checker written in Common Lisp, so maybe this book has some clues.
<Pixel_Outlaw>
I managed to snag a copy for 17 bucks. Well see!
<Pixel_Outlaw>
*will
<beach>
Congratulations!
<Pixel_Outlaw>
I've found some older Lisp books (Scheme in particular) are written in a bad style of huge monolithic functions. Hoping it's not the case here.
<aeth>
odd
<Pixel_Outlaw>
THOU SHALT NOT HAVE ANY MACRO BEFORE PROG
<Pixel_Outlaw>
:P
<aeth>
I wonder when small functions became the fashionable thing to do in Lisps
<Pixel_Outlaw>
Probably as Lisp grew more expressive. A lot of the old PROG code is very blockish but as people started abstracting into LET code got more modular.
<Pixel_Outlaw>
I'm only going by very old Lisp books.
<ixelp>
GitHub - ddmcdonald/sparser: A natural language understanding system for English
<beach>
pranav: Interesting! Thanks! However, I find that most existing parsers are meant for understanding or translation, and I think that grammar checking has very different requirements. I could be wrong of course.
<beach>
pranav: But I should definitely look into it.
<ixelp>
Advanced compiler design and implementation : Muchnick, Steven S., 1945- : Free Download, Borrow, and Streaming : Intern [...]
<beach>
Great! You might want to photocopy the bibliographies.
rozenglass has quit [Ping timeout: 252 seconds]
<beach>
As I have said in the past, the book is good for giving an overview of what is possible, and the names of the different techniques, but its algorithmic language is no good, so I always go to the original paper when I want to understand the details.
waleee has joined #commonlisp
<younder>
What paper?
<beach>
Whatever paper is mentioned in the book for a particular algorithm.
<younder>
ah
<beach>
Like, the book will say "Algorithm so and so" and then give his own code for it (which sucks) and then the bibliography that says what paper the algorithm came from.
edgar-rft_ has joined #commonlisp
edgar-rft has quit [Ping timeout: 258 seconds]
rozenglass has joined #commonlisp
awlygj has joined #commonlisp
Cymew has joined #commonlisp
awlygj has quit [Ping timeout: 252 seconds]
decweb has joined #commonlisp
waleee has quit [Ping timeout: 245 seconds]
green_ has joined #commonlisp
Cymew has quit [Quit: Konversation terminated!]
amb007 has quit [Read error: Connection reset by peer]
amb007 has joined #commonlisp
bobcave has quit [Quit: Leaving]
prokhor_ has quit [Remote host closed the connection]
varjag has quit [Quit: ERC (IRC client for Emacs 27.1)]
<Akbar-Birbal>
SBCL isn't loading this file, though I can see it in HELM. Can't find the issue.
<Akbar-Birbal>
(Note: not solved by using .lisp extension or giving an absolute path)
<Akbar-Birbal>
I am using spacemacs with some common layers like common lisp. I posted this message earlier in a xmpp group. I would be grateful if someone can point out the issue.
<scymtym>
LOAD merges relative pathnames with *DEFAULT-PATHNAME-DEFAULTS*, not the unix current directory
<random-nick>
do you mean getting the form as a value (what beach referred to) or going back in input history (like in bash)? if it's the latter, sbcl does not have that feature, you have to use something which wraps sbcl's repl
<beach>
Akbar-Birbal: What random-nick says. Typically you would use something like SLIME, and then you use the M-P or M-r or something like that for the REPL history.
<Akbar-Birbal>
Aah. Thanks for the pointer. I will try to turn M-p and M-r into some evil bindings in my spacemacs.
<Akbar-Birbal>
Is it intentional by sbcl devs to not add this history feature, or a limit on resources?
<beach>
The former.
<Akbar-Birbal>
Why?
<beach>
It is a much better idea to have this done by some separate software that can be used with all Common Lisp implementations, than to re-implement it in each Common Lisp implementation.
<Akbar-Birbal>
Why? just curious.
<beach>
Simple code factoring in other words.
<beach>
Decrease the global maintenance burden. Elementary software engineering.
<Akbar-Birbal>
Aah. I get it. Thanks for all the help beach random-nick and scymtym.
<beach>
Pleasure.
<beach>
For a single-implementation language, there is no difference, but for something like Common Lisp with many implementations, the difference is great.
lucasta has quit [Remote host closed the connection]
akovalenko has joined #commonlisp
varjagg is now known as varjag
yitzi has joined #commonlisp
remexre has joined #commonlisp
mgl has quit [Ping timeout: 252 seconds]
randm has quit [Remote host closed the connection]
randm has joined #commonlisp
Akbar-Birbal has left #commonlisp [#commonlisp]
randm has quit [Remote host closed the connection]
randm has joined #commonlisp
contrapunctus has quit [Ping timeout: 258 seconds]
mgl has joined #commonlisp
contrapunctus has joined #commonlisp
contrapunctus has quit [Ping timeout: 258 seconds]
mgl has quit [Ping timeout: 245 seconds]
chsasank has quit [Ping timeout: 248 seconds]
shawnw has quit [Ping timeout: 248 seconds]
McParen has joined #commonlisp
contrapunctus has joined #commonlisp
contrapunctus has quit [Ping timeout: 272 seconds]
randm has quit [Remote host closed the connection]
randm has joined #commonlisp
mgl has joined #commonlisp
cercopith has quit [Remote host closed the connection]
contrapunctus has joined #commonlisp
dawids_ has joined #commonlisp
mgl has quit [Ping timeout: 265 seconds]
contrapunctus has quit [Ping timeout: 244 seconds]
attila_lendvai has joined #commonlisp
zxcvz has joined #commonlisp
awlygj has quit [Remote host closed the connection]
zxcvz has quit [Client Quit]
Pixel_Outlaw has joined #commonlisp
McParen has left #commonlisp [#commonlisp]
mwnaylor has joined #commonlisp
cage has quit [Quit: rcirc on GNU Emacs 29.4]
waleee has joined #commonlisp
bilegeek has joined #commonlisp
chsasank has joined #commonlisp
JuanDaugherty has joined #commonlisp
attila_lendvai has quit [Ping timeout: 258 seconds]
contrapunctus has joined #commonlisp
xlymian has quit [Ping timeout: 276 seconds]
contrapunctus has quit [Ping timeout: 248 seconds]
mgl has joined #commonlisp
traidare has quit [Quit: WeeChat 4.3.5]
Perflosopher has joined #commonlisp
Perflosopher0 has quit [Ping timeout: 276 seconds]
yitzi has quit [Remote host closed the connection]
mgl has quit [Ping timeout: 264 seconds]
pve has quit [Quit: leaving]
shka has quit [Ping timeout: 272 seconds]
spdegabrielle has quit [Quit: Connection closed for inactivity]
NotThatRPG has quit [Ping timeout: 255 seconds]
wacki has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
xlymian has joined #commonlisp
dawids_ has quit [Quit: Leaving]
xlymian has quit [Read error: Connection reset by peer]
xlymian has joined #commonlisp
zxcvz has joined #commonlisp
zxcvz has quit [Client Quit]
eddof13 has joined #commonlisp
eddof13 has quit [Client Quit]
varjag has quit [Ping timeout: 255 seconds]
akoana has joined #commonlisp
johnjaye has quit [Ping timeout: 252 seconds]
eddof13 has joined #commonlisp
eddof13 has quit [Client Quit]
xlymian` has joined #commonlisp
xlymian has quit [Read error: Connection reset by peer]
NotThatRPG has joined #commonlisp
xlymian` has quit [Ping timeout: 276 seconds]
amb007 has quit [Ping timeout: 252 seconds]
johnjaye has joined #commonlisp
skeemer has quit [Ping timeout: 260 seconds]
<mwnaylor>
If I write an asdf module (A) that depends upon another module (B), should B containo a (load-module B) form?
JuanDaugherty has quit [Quit: JuanDaugherty]
<mwnaylor>
s/containo/contain/
<bike>
no, you should just express the dependencies in the asdf component definition. :depends-on
<mwnaylor>
bike: good advice. TBH, I've only recently learned about modules. I "cargo cult" creation, since I don't have the process burned into my mind. I basically (info "stumpwm") and follow the documentation there for module creation.
<mwnaylor>
Actually, this is more direct: (info "(stumpwm) writing modules").
<aeth>
build systems, ASDF included, are basically programming-by-copy-and-paste... you figure it out once and then copy and paste it into everything you do from then on
<aeth>
I think it's just the problem space
<mwnaylor>
Ok, then I feel a little less foolish.
<mwnaylor>
I'll need to learn more about ASDF. Currently only using it minimally in a subdirectory dedicated to stumpwm modules.
<mwnaylor>
Is there an emacs package that automates creating an ASDF system?