Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • 17
    \$\begingroup\$ I liked the Unlambda answer, but this one is (IMHO) too much of a stretch, as it is obviously the interpreter itself which leaks the memory, i.e. I get ` definitely lost: 7,742 bytes in 14 blocks` when I run perl --version on my machine, despite it never gets to running any program, at all. \$\endgroup\$ Commented Feb 19, 2017 at 7:14
  • 12
    \$\begingroup\$ @zeppelin: Agreed, but according to our rules, it's the implementation that defines the language, thus if the implementation leaks memory, all programs in the language leak memory. I'm not necessarily sure I agree with that rule, but at this point it's too entrenched to really be able to change. \$\endgroup\$ Commented Feb 19, 2017 at 9:03
  • 9
    \$\begingroup\$ This also works in Node JS. \$\endgroup\$ Commented Feb 19, 2017 at 18:40
  • 7
    \$\begingroup\$ This feels like a new standard loophole in the making... \$\endgroup\$ Commented Feb 22, 2017 at 3:32
  • 57
    \$\begingroup\$ Finally a Perl script that I can understand. \$\endgroup\$ Commented Feb 22, 2017 at 16:05