Skip to main content

Timeline for Count up folks!

Current License: CC BY-SA 3.0

10 events
when toggle format what by license comment
Jun 17, 2020 at 9:04 history edited CommunityBot
Commonmark migration
Apr 28, 2016 at 13:58 history edited Robert Benson CC BY-SA 3.0
added 238 characters in body
Apr 27, 2016 at 4:42 review Suggested edits
Apr 27, 2016 at 4:58
Apr 26, 2016 at 11:10 comment added Erik the Outgolfer @OlivierDulac I prefer to say 'vote' for comments and 'upvote' for answers.
Apr 26, 2016 at 6:55 comment added Olivier Dulac @RobertBenson: If you edit (gain 2 bytes by taking out the curly braces around the printf, for example, and include a note showing the way to invoke it (like the one in your last comment), you'll gain 2 bytes + I would be able to revert my downvote to a vote. (right now it's locked "until it is edited")
Apr 25, 2016 at 17:28 comment added Robert Benson @rexkogitans I agree that not initializing j=0 is ugly and I would never do it in production code... but this is PPCG :)
Apr 25, 2016 at 17:27 comment added Robert Benson @OlivierDulac I can't use <$1 since j starts at 0, the first ++ gets it up to 1, so I need the <=. I didn't think I would need the awk "..." part since this could simply be placed in a file and called however you like (essentially like compiling a file in other languages). E.g. awk -f FILE <<< 21657
Apr 25, 2016 at 15:40 comment added Olivier Dulac should be "<$1" (you go from 0 to $1-1, as you ++ before you print). You can also drop the {} after while, as you only have 1 command : {for(;j<$1;)print++j} . But : $1 is not valid in awk.. you're mixing shell's variable and awk variables. If you want $1, you also need to add the awk "..." wrapping ...
Apr 25, 2016 at 15:02 comment added rexkogitans Not initialising with j=0 is ugly but ok here. :-)
Apr 25, 2016 at 14:22 history answered Robert Benson CC BY-SA 3.0