I see. My reason was to get in touch, we used to collaborate on sed answers, but I took a long break. I guess I'll check his profile from time to time for activity.
hi, quick question: if I add a comment to my own solution, or edit it, will the person that initially downvoted see that/get notified? I don't mind a downvote once in a while, but it is sad I don't have any feedback as to why, since the submission is correct.
@user41805 Based on that 2nd link, are you telling me there's a 99 byte solution? Or even a 30 byte solution???? If so, then I definitely have to find one below 100 bytes. But for the rep, 126 is enough.
It was a dirty trick, the result is still the same code, so I don't want to post it as a new answer. If I send it to you here or as a comment to your original answer, can you send me directly the rep?
@user202729 I agree. I already found a shorter 3 char version with 1ZP. My intuition tells me there are other 3 char dc solutions out there, much shorter than 3.6Kb.
I guess you can split your code into multiple such 16 Tb files, but then the OS needs to give to dc probably 122*2 Tb (source and stack). Surely no current PC can do that.
@user202729 your dc answer can't run on any architecture, because of the RAM first of all, then the limitation to the maximum file size. Still, I liked your answer.
There are a few operators in dc that work with a single number, but besides Z, perhaps v (square root) can be used, but I highly doubt it one can be that lucky. (as explained above).
@user41805 In fact I suspect there are multiple 3 char solutions possible, besides the trivial ones of replacing 1 in my answer with any digit from 1 to 9. For example, one can use multiple v operations to do successive square roots from an incredibly large unary number until you get to the ASCII code.
@user41805 your bounty brought me back to make new bash, sed and dc answers and I was shocked no one thought of the trivial dc answer to that question. I posted it at codegolf.stackexchange.com/a/218683/59010
I'm a bit young to remember the IRC and usenet :D Though I caught them, it was only for 2 years and never used them, since better alternatives already existed at that time.
@StéphaneChazelas Thank you for the good discussion, I'll try to remember some points here. Should we delete the last 4 comments from your submission? (starting with @seshoumara, GNU sed can do it with \L as you...)
Until now I was living only in the GNU Linux world, a few days ago for the first time I had to run a sed script using the busybox version, it didn't run, because I use GNU extensions all the time, I got so much used to them. That's why I don't know what is working on a version and what is not, what is portable (posix I assume) and what is not.
I know you can't have anything after i,c,a,r,w,e; but in GNU sed at least you can continue after :;b,t,} and no ; is needed before }. I hate all these different implementations.