boss: your mission, should you choose to accept it,
super hacker: this better be good
boss: is to write a program that takes in valid DD/MM/YYYY dates and outputs milliseconds since epoch,
super hacker: below my pay grade old man
boss: in brainfuck
super hacker: Now We're Talking
@typhlosion i want to try to write this in befunge98 just to see if i can
the real question is
unix epoch or julian date epoch
@typhlosion okay so i was working on this but for some reason befunge98 thinks 17368 days plus 1970/1/1 is 24/5/17373 which is
very wrong
@boots is it that befunge thinks it, or that your algorithm thinks it
@typhlosion im pretty sure it's either befunge being bad or the befunge's docs being bad
@boots wait, are you using some kind of date fingerprint or are you doing the logic yourself
also what interpreter are you using
@typhlosion im using the date fingerprint in cfunge
first output is the stack before A
second output is the stack after A
https://computerfairi.es/media/LnBnofP_O4wZ3r0Des0
@typhlosion im not seeing what's going wrong here because according to docs it should give 1970 1 6
http://rcfunge98.com/rcsfingers.html#DATE
https://computerfairi.es/media/T7V5b3NvYU-6Du7t0Yg
@typhlosion the weirdest part is mycology passes so i dont see whats wrong with my implementation specifically
here's my code
https://ghostbin.com/paste/b5kes
change <<> to <>> for stack before A
@boots at a glance: this code looks like you're putting the operands in the wrong order (days d m y TOP, rather than y m d days TOP)
@typhlosion alright i finished and then realized i did the exact reverse of the actual program intended but uhh https://ghostbin.com/paste/qtrpg
@boots why 2k. rather than just ..
@typhlosion because i was using 4k. before and i didnt want to bother with adding and removing spaces
@boots i guess that's fair, albeit still ridiculous
@typhlosion id say its pretty good for my first program in befunge-98 /shrug
@boots it's not bad! befunge is a really fun language to mess around with
have you seen the IRC bot written in it?
@typhlosion yeah!
did not get it working, but
yeah
@boots it says on the page (Notes section under the ToC) that arguments and outputs are listed left-to-right from bottom to top, but it's easy to miss if you go from ToC straight to the thing you wanted to look for