Timeline for Split string into 160-character chunks while adding text to each part
Current License: CC BY-SA 3.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 14, 2016 at 18:26 | answer | added | jefflunt | timeline score: 0 | |
Jul 14, 2016 at 14:54 | comment | added | jefflunt | Your maximum text length can be 10^70 ? That's 10^67 times more than all the data humanity has stored since the 1980s. | |
Jul 2, 2016 at 14:45 | answer | added | tokland | timeline score: 2 | |
Jul 1, 2016 at 23:01 | history | edited | 200_success | CC BY-SA 3.0 |
added 2 characters in body; edited tags; edited title
|
Jul 1, 2016 at 22:52 | answer | added | sschmeck | timeline score: 1 | |
Jul 1, 2016 at 7:24 | history | edited | tokland | CC BY-SA 3.0 |
added 4 characters in body
|
Jul 1, 2016 at 7:01 | comment | added | Aaron | Ah, when you said "without adding more conditions" I took that to also mean using this approach. | |
Jul 1, 2016 at 3:11 | comment | added | Wojciech Bednarski | @Aaron You are more than welcome to change the approach, this is why I posted code here. | |
Jul 1, 2016 at 2:57 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 47 characters in body
|
Jul 1, 2016 at 2:55 | comment | added | Aaron | Sorry, without adding more conditions or changing your approach, I don't see a way to support more messages or eliminate the occasionally 1-byte difference. Regex and String.scan just aren't dynamic enough, as far as I can tell. | |
Jul 1, 2016 at 2:44 | comment | added | Wojciech Bednarski | @Aaron Yeah, I know we are wasting 1 byte here. But it is the tiniest problem here. | |
Jul 1, 2016 at 2:36 | comment | added | Aaron | It's worth noting that your current code will make 159-character messages for the first 9 parts of a text with 10 or more parts, because " - Part 9 of 10" is only 15 characters. | |
Jul 1, 2016 at 2:14 | review | First posts | |||
Jul 1, 2016 at 2:58 | |||||
Jul 1, 2016 at 2:10 | history | asked | Wojciech Bednarski | CC BY-SA 3.0 |