selwyn has quit [Read error: Connection reset by peer]
hendursa1 has quit [Remote host closed the connection]
McParen has joined #lisp
karlosz has quit [Quit: karlosz]
selwyn has joined #lisp
McParen has left #lisp [#lisp]
aartaka_d has quit [Read error: Connection reset by peer]
aartaka has joined #lisp
engblom has joined #lisp
engblom has left #lisp [#lisp]
hendursa1 has joined #lisp
pve has left #lisp [#lisp]
amk has quit [Remote host closed the connection]
v88m has quit [Ping timeout: 240 seconds]
paulj has joined #lisp
Cymew has joined #lisp
Cymew has left #lisp ["Konversation terminated!"]
aartaka_d has joined #lisp
aartaka has quit [Ping timeout: 240 seconds]
aartaka has joined #lisp
amk has joined #lisp
aartaka_d has quit [Ping timeout: 258 seconds]
random-nick has joined #lisp
d4ryus has quit [Quit: WeeChat 3.1]
d4ryus has joined #lisp
paulj has quit [Quit: ERC (IRC client for Emacs 27.2)]
shifty has quit [Ping timeout: 265 seconds]
shifty has joined #lisp
Ziemas has left #lisp ["WeeChat 3.1"]
dhil has joined #lisp
shifty has quit [Ping timeout: 265 seconds]
shifty has joined #lisp
Stanley00 has quit []
kevingal has joined #lisp
scymtym has joined #lisp
gaqwas has joined #lisp
wilfredh has quit [Quit: Connection closed for inactivity]
shifty has quit [Ping timeout: 265 seconds]
shifty has joined #lisp
zymurgy has quit [Quit: WeeChat 1.4]
killsushi has quit [Quit: Leaving]
davros has quit [Remote host closed the connection]
long4mud has joined #lisp
gaqwas has quit [Remote host closed the connection]
absolutezer0 has joined #lisp
aartaka_d has joined #lisp
aartaka has quit [Ping timeout: 260 seconds]
<absolutezer0>
Hey beach :) yea I'm new here....When i use the y-or-n-p a new-line gets automatically printed in output(which is not expected) could you please help me resolve this ? im using sbcl 2.0
<phoe>
"This use is now deprecated and will cease to be supported in a future version."
<phoe>
woop
selwyn has quit [Remote host closed the connection]
<phoe>
absolutezer0: this is PCL
selwyn has joined #lisp
<phoe>
I remember this issue from before, one second...
APic has quit [Quit: Trying to switch to Libera.Chat]
Aurora_v_kosmose has quit [Remote host closed the connection]
<absolutezer0>
Yea
Aurora_v_kosmose has joined #lisp
<phoe>
yes, I recognize this
<phoe>
the issue is that y-or-n-p is not specified to output strictly the kind of output PCL requires
<phoe>
so if you want to have full control over newlines, you'd need to implement it in a way that fits your needs
<absolutezer0>
How do I do that?
<phoe>
in general, (defun my-y-or-n-p (...) ...)
<phoe>
if you don't feel confident enough in doing that, you might bear with your Lisp implementation and simply try to ignore that newline for now until you progress further into PCL
selwyn has quit [Read error: Connection reset by peer]
selwyn has joined #lisp
Grauwolf has quit [Quit: WeeChat 3.1]
Grauwolf has joined #lisp
<absolutezer0>
Ohhh ok, thank you so much! Could also point me to some other awesome lisp resources?
<rpg>
Xach: Sorry about the iterate issues, but there was an old bug in ITERATE that really *was* a bug, and it's impossible to fix it w/o causing problems. But you should see only single warnings per affected library.
zaquest has joined #lisp
<rpg>
If you like, I could suggest a recipe you could put in to avoid this problem.
<rpg>
But it really is something bad, and we can't just leave it in.
<Xach>
rpg: ok. i will report bugs to the broken library authors.
<Xach>
"a single warning" breaks building on SBCL
<rpg>
Xach: That would be good, and if you need a wrap-around for this, there's a special warning class that could be muffled.
<rpg>
Xach: Quick summary -- ITERATE mistakenly defines COUNT as an iterate clause keyword, but that conflicts with CL, because the codewalker has no way to know if the programmer wanted CL:COUNT or iterate's interpretation of COUNT. The original paper clearly states that cases like that (conflicts with CL) should NOT be defined in ITERATE.
<rpg>
With the benefit of hindsight, I wish that NONE of these had been defined, and that EVERYTHING was of the COUNTING form...
* rpg
will check to confirm that this warning class is exported.
<Xach>
It doesn't make any sense to muffle the warning for an aggregator like me. That just means it will fail when other people try to load it without muffling. And there's no gradual phase-out with a full cl:warn warning. It won't build on SBCL under default settings.
<Bike>
sbcl has an internal deprecation system that starts with a style warning and then becomes a full warning as it gets more and more obsolete, which seems reasonable
<Bike>
it goes early = style warning when compiling, late = warning when compiling, final = warning when compiling and error when running
<Xach>
quicklisp contributes to problems in this area by muffling build output too much, but i don't know a good fix for the situation
edgar-rft has quit [Remote host closed the connection]
<rpg>
Xach: OK, I had forgotten to export the warning. Quick question for advice: should I rename it something obscure like ITERATE-CLAUSE-DEPRECATION-WARNING ? That's a mouthful of marbles, but would be less likely to cause pain for people who USE iterate than would DEPRECATION-WARNING.
edgar-rft has joined #lisp
<rpg>
I'm trying to not be difficult, but it's hard in this case, where the mistake was baked in so long ago.
<rpg>
Anyway, the quick fix is to use COUNTING instead of COUNT, or ... if they *wanted* CL:COUNT, they need to switch to FUNCALL or something awful like that.
<rpg>
Or... maybe I should just do something real fancy like export it from `ITERATE-WARNINGS` package.
absolutezer0 has quit [Quit: Connection closed for inactivity]
whitgreenlghtsbr is now known as GIANT_WORLDKEEPE
GIANT_WORLDKEEPE is now known as GIANTWORLDKEEPER
<rpg>
`iterate-warnings:deprecation-warning` is probably the best choice, so as to make it clear it's public, but also not take a chance of breaking code that USEs ITERATE.
<Bike>
or some kind of iterate plumbing package more generally
<rpg>
Bike: `iterate-conditions`?
GIANTWORLDKEEPER has quit [Quit: EXIT]
<rpg>
Bike: these are not internal things -- they are just things people need to know about, but that can't be exported without danger of messing up the environment. So not really plumbing -- or at least not INTERNAL plumbing
<rpg>
Xach: If you like, I could apply a `release` tag or branch to ITERATE while we dial this in. You could test with master, but not incorporate until things shake out.
absolutezer0 has joined #lisp
<Xach>
rpg: i think a branch would be helpful at the moment. i was hoping to make a quicklisp release soon, and having a temporary repreive would help give people a little more time to fix things before they are dropped from quicklisp.
<Xach>
I also understand if you'd rather not do that - it's up to you how much effort you want to put forth.
<rpg>
Xach: OK, I will make a release branch.
<Xach>
Sometimes libraries are abandoned and will never be fixed, and the delay doesn't matter
<rpg>
Xach: I have just pushed `release`. It's set to 1.5.2, which fixes a couple of bugs, but in what I think are non-visible ways. If this still causes pain, LMK. (I will be AFK for a little while -- you can reach me by email or minion)
<rpg>
I can roll back release farther, if necessary, but I would prefer to get these two fixes out there.
<Xach>
rpg: thanks, i'll test with that.
klltkr has joined #lisp
jmiven has quit [Quit: reboot]
attila_lendvai has joined #lisp
ggoes has quit [Quit: WeeChat 2.3]
ggoes has joined #lisp
spal has joined #lisp
spal has quit [Client Quit]
ggoes has quit [Client Quit]
ggoes has joined #lisp
GIANTWORLDKEEPER has joined #lisp
frost-lab has quit [Quit: Connection closed]
Major_Biscuit has joined #lisp
sp41 has joined #lisp
Major_Biscuit has quit [Quit: WeeChat 3.0.1]
klltkr has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]