Timeline for Output Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo
Current License: CC BY-SA 4.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 1, 2021 at 21:53 | comment | added | Arnauld | Ah yes, sorry about that. | |
Feb 1, 2021 at 21:38 | comment | added | gastropner | @Arnauld Very nice. Sadly, I lost compliance using it, so must find a way around it. | |
Feb 1, 2021 at 21:30 | history | edited | gastropner | CC BY-SA 4.0 |
added 112 characters in body
|
Feb 1, 2021 at 12:21 | comment | added | anotherOne | Pardon my ignorance please. I thought the null character was literally nothing when printed. | |
Feb 1, 2021 at 6:38 | comment | added | Peter Cordes |
@Davide: the question says to output the string as shown. It doesn't say "so it looks the same on a terminal which ignores 0 bytes", so you're not allowed to print garbage bytes like ASCII 0 at the end. That would be noticeable piping into hexdump -C , or redirecting to a file. Tabs instead of spaces is maybe justifiable, especially since standard tab-stops are 8 spaces, and "buffalo" is 7 letters long.
|
|
Feb 1, 2021 at 3:28 | comment | added | gastropner | @Davide No, if you order printf to print a NUL character, a NUL character will be printed. It won't magically disappear. | |
Feb 1, 2021 at 3:27 | comment | added | gastropner | @Arnauld Neato! | |
Feb 1, 2021 at 3:27 | history | edited | gastropner | CC BY-SA 4.0 |
added 94 characters in body
|
Jan 31, 2021 at 21:21 | comment | added | anotherOne | 0 would be the null character, so you don't print nothing more than your buffaloes. However in TIO the 0 is displayed as an empty rectangle, so we have to use a newline at the end. | |
Jan 31, 2021 at 18:58 | comment | added | gastropner | @Davide Ehhh tab is not the same as space, so I disagree that 9 is a replacement for 32. Also not sure what you mean by 0 instead of 10; same thing there: Different characters. | |
Jan 31, 2021 at 3:05 | comment | added | anotherOne |
I noticed that in TIO is not possible to use 0 (that is the right character to use) in place of 10 , so to regain the byte lost, I checked for a substitute of 32 and found that 9 works.
|
|
Jan 31, 2021 at 2:22 | history | answered | gastropner | CC BY-SA 4.0 |