Skip to main content

<><><>

One of the first things I looked at when moving the Minimal-2D code was verifying that I could move <><><> along with it. If I was going to deal with 2D polyglot transversalism, I was going to deal with all transgressions. I basically luck sacked my way into the solution of putting ;n4 at the end of line 1 and moving the \D further back in line 1. BTW, I didn’t know that <><><> could be directed down before answer 40 since it’s been so well contained. I’d like to think this could be used later to diverge <><><> from another similar language.

<><

One of the first things I looked at when moving the Minimal-2D code was verifying that I could move <>< along with it. If I was going to deal with 2D polyglot transversalism, I was going to deal with all transgressions. I basically luck sacked my way into the solution of putting ;n4 at the end of line 1 and moving the \D further back in line 1. BTW, I didn’t know that <>< could be directed down before answer 40 since it’s been so well contained. I’d like to think this could be used later to diverge <>< from another similar language.

><>

One of the first things I looked at when moving the Minimal-2D code was verifying that I could move ><> along with it. If I was going to deal with 2D polyglot transversalism, I was going to deal with all transgressions. I basically luck sacked my way into the solution of putting ;n4 at the end of line 1 and moving the \D further back in line 1. BTW, I didn’t know that ><> could be directed down before answer 40 since it’s been so well contained. I’d like to think this could be used later to diverge ><> from another similar language.

replaced http://codegolf.stackexchange.com/ with https://codegolf.stackexchange.com/
Source Link

First off, I want to say how awesome @SnoringFrog’s Versatile Integer PrinterVersatile Integer Printer Score Rundown code snippet from the last post was. I’ve been calculating answers before posting for a while, and this has re-inspired me keep it small. I think we can beat @sp3000’s answer eventually.

So I started working on this answer by trying to golf down what I could and I was pretty successful. I even had an answer in a different language with a total byte count smaller than #40. But as I tried to golf down Minimal-2D, I had to learn BF so I could better work with its derivatives and in the process I found @Primo’s record breaking Hello, World!Hello, World!. I fell in love the elegance.

First off, I want to say how awesome @SnoringFrog’s Versatile Integer Printer Score Rundown code snippet from the last post was. I’ve been calculating answers before posting for a while, and this has re-inspired me keep it small. I think we can beat @sp3000’s answer eventually.

So I started working on this answer by trying to golf down what I could and I was pretty successful. I even had an answer in a different language with a total byte count smaller than #40. But as I tried to golf down Minimal-2D, I had to learn BF so I could better work with its derivatives and in the process I found @Primo’s record breaking Hello, World!. I fell in love the elegance.

First off, I want to say how awesome @SnoringFrog’s Versatile Integer Printer Score Rundown code snippet from the last post was. I’ve been calculating answers before posting for a while, and this has re-inspired me keep it small. I think we can beat @sp3000’s answer eventually.

So I started working on this answer by trying to golf down what I could and I was pretty successful. I even had an answer in a different language with a total byte count smaller than #40. But as I tried to golf down Minimal-2D, I had to learn BF so I could better work with its derivatives and in the process I found @Primo’s record breaking Hello, World!. I fell in love the elegance.

added 4 characters in body
Source Link
Chance
  • 5.4k
  • 39
  • 30

Befunge-98 also had a command (') to take the asciascii code of the next character. So, '1, takes the code asci code for the character 1, puts it on the stack and then prints the ascii character for the top value on the stack with ,. Just gotta do this twice to print 11 and drop a q to quit out gracefully.

I’ve talked about some of Perl6’s <> balancing issues elsewhere in this answer, so I’m not going to go over it again. But I do want to point out that I moved #>27.say# to the second to last line. This doesn’t have a functional purpose in this answer. I actually made this move to satisfy a different answer that I ended up not using this round. I decided to just leave it since I plan to post that answer at my next opportunity and I didn’t want to bother undoing and re-doing it.

Befunge-98 also had a command (') to take the asci code of the next character. So, '1, takes the code asci code for the character 1, puts it on the stack and then prints the ascii character for the top value on the stack with ,. Just gotta do this twice to print 11 and drop a q to quit out gracefully.

I’ve talked about some Perl6’s <> balancing issues elsewhere in this answer, so I’m not going to go over it again. But I do want to point out that I moved #>27.say# to the second to last line. This doesn’t have a functional purpose in this answer. I actually made this move to satisfy a different answer that I ended up not using this round. I decided to just leave it since I plan to post that answer at my next opportunity and I didn’t want to bother undoing and re-doing it.

Befunge-98 also had a command (') to take the ascii code of the next character. So, '1, takes the code asci code for the character 1, puts it on the stack and then prints the ascii character for the top value on the stack with ,. Just gotta do this twice to print 11 and drop a q to quit out gracefully.

I’ve talked about some of Perl6’s <> balancing issues elsewhere in this answer, so I’m not going to go over it again. But I do want to point out that I moved #>27.say# to the second to last line. This doesn’t have a functional purpose in this answer. I actually made this move to satisfy a different answer that I ended up not using this round. I decided to just leave it since I plan to post that answer at my next opportunity and I didn’t want to bother undoing and re-doing it.

typos
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
small formatting thing.
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
Bounty Ended with 100 reputation awarded by CommunityBot
a couple more typos
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
typo
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
added 5108 characters in body
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
Minor corrections in walkthrough to match polyglor changes.
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
shaved 2 more bytes, since I was already in here.
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
typo
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
Incident Tokens. *sigh*
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading
Source Link
Chance
  • 5.4k
  • 39
  • 30
Loading