☃️ - 2023 DAY 4 SOLUTIONS -☃️
☃️ - 2023 DAY 4 SOLUTIONS -☃️
Day 4: Scratchcards
Megathread guidelines
- Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
- Code block support is not fully rolled out yet but likely will be in the middle of the event. Try to share solutions as both code blocks and using something such as https://topaz.github.io/paste/ or pastebin (code blocks to future proof it for when 0.19 comes out and since code blocks currently function in some apps and some instances as well if they are running a 0.19 beta)
FAQ
- What is this?: Here is a post with a large amount of details: https://programming.dev/post/6637268
- Where do I participate?: https://adventofcode.com/
- Is there a leaderboard for the community?: We have a programming.dev leaderboard with the info on how to join in this post: https://programming.dev/post/6631465
🔒This post will be unlocked when there is a decent amount of submissions on the leaderboard to avoid cheating for top spots
🔓 Unlocked after 8 mins
You're viewing a single thread.
Language: C
Another day of parsing, another day of
strsep()to the rescue. Today was one of those satisfying days where the puzzle text is complicated but the solution is simple once well understood.Code (29 lines)
int main() { char line[128], *rest, *tok; int nextra[200]={0}, nums[10], nnums; int p1=0,p2=0, id,val,nmatch, i; for (id=0; (rest = fgets(line, sizeof(line), stdin)); id++) { nnums = nmatch = 0; while ((tok = strsep(&rest, " ")) && !strchr(tok, ':')) ; while ((tok = strsep(&rest, " ")) && !strchr(tok, '|')) if ((val = atoi(tok))) nums[nnums++] = val; while ((tok = strsep(&rest, " "))) if ((val = atoi(tok))) for (i=0; iLooks like Lemmy's odd parsing broke your comment at the less-than sign.
That's unfortunate, although it looks good on my instance (SDF). Anything I could do?
Ohh that’s interesting, I’ve seen a few comments about mishandling of special chars in code blocks and assumed it was a server issue, maybe it’s fixed in newer releases or perhaps it’s client side.