James Holderness

Don't want to make any promises, because I don't have a lot of free time now that I have a job, but I'm very keen to get this working. Will let you know if/when I get something up and running.

If I were to write something like that, would you have any interest in adding it to TIO?

@Dennis On an unrelated note, I had an idea for adding ANSI escape code support to TIO. Essentially just a small ANSI-to-HTML utility through which you could pipe the output of any interpreter. The resulting markup would then be injected into a div or code block on the frontend instead of the current textarea.

I don't know. If it was up to me, I think I would feel more comfortable applying options to the compiler to try and make the undefined behaviour consistent, rather than reimplementing the entire language from scratch.

Sorry if I'm being argumentative here. Don't really really feel strongly about it. Just surprised me is all.

Yes. But I knew I was relying on undefined behaviour. And anyone relying on undefined behaviour in C could just as easily have had their answers break in a similar way (as frequently happens in the real world).

@Dennis The spec explicitly defines the memory cell type as a C signed char, which assumedly includes all of the undefined behaviour that goes along with that choice. I guess you can assume that was a bad choice, or a mistake, but it seems to me like you're second guessing the language author at that point.

@Dennis Given that's the reference implementation, surely that undefined behaviour is part of the language. I'm assuming you wouldn't fork a C compiler just because certain aspects of C are undefined?

Don't think it makes any difference. Just thought it was weird.

@NieDzejkob The spec defines ooo as p++, while the TIO implementation translates [a-z][a-z][a-z] to --p

Not that I'm likely to be using oOo, or any other brainfuck variant for that matter, but I thought the memory size option on the oOo reference implementation might be useful.

The obvious differences I noticed were that the memory was unsigned and the memory pointer direction was reversed. But as I said, I don't think those differences actually matter. I was just surprised that TIO doesn't always using reference implementations.

I'm not sure it really makes any difference in this case, except that you're losing some of the functionality that the reference interpreter and compiler support via command line options.

@Dennis I notice you recently added oOo CODE to TIO, but you seem to be using a proprietary transpiler which doesn't technically match the language specification. I always assumed you'd use the reference implementation for a language when available?

Although I'm curious whether @user202729 is in the same situation as me or they're having a different issue.

@Dennis Not a major concern. I can't imagine there are a huge number of desktop users with touch capability that are also using Firefox.

Oddly enough this is only a problem on Firefox. On Chrome and Edge the touch functionality doesn't appear to be detected so the autofocus works.

@Dennis FYI, the code textarea doesn't autofocus for me either. Seems to be because my laptop is being detected as a touch device (which technically it is).

And yes, somebody did point out the dubiousness of the Latin being used.

He also had quattre and hexe at one point instead of quadre and sexe, but I think the latter were the preferred choice.

But I've just been doing some digging through the old Befunge mailing list to see whether they discussed any of this back in the day, and I see that the prefixes being suggested back then (by Pressey himself) were une, be, tre, quadre, quinte, sexe and septe.

@Dennis Neither my Latin nor my French are good enough to have realised that quinte was wrong. :)

Thanks @Dennis. It's really great to have these versions easily accessible now. But for the names, wouldn't Sextefunge or Sexefunge be more appropriate for 6, given the Latin theme? And for 7, surely Septefunge rather than Septifunge?

Otherwise you can just use a regular 93 version of hello world, which should work everywhere.

And this one should work only on 97: q"Hello, World!"i#]:#,_@

Btw, if you'd like a version-specific hello world, this one should work only on 96: "Hello, World!"i>:#,_@

As for the language variations - I think it's safe to ignore the dimension options until someone specifically requests them, otherwise it's going to really get out of hand. There's a good chance they'll never be used, and if anyone desperately wanted them they could just use the base Befunge-97 language and override the dimension with a command line argument.

@Dennis That's even better. I couldn't get the UNIX link to work before, so I thought it just hadn't been picked up by the archiver.

OK. Thanks

It was originally written for DOS, but should just require an updated makefile for Linux. If it helps any, this is what I use: gist.github.com/anonymous/5d064eb65a43808e3992f999c86cffa2

Last known version of the source can be found on the internet archive: web.archive.org/web/20000903032423/http://www.mines.edu:80/…

@Dennis I don't know how you feel about having too many versions of Befunge on TIO, but if it doesn't bother you, it might be nice to add MTFI. It's one of the only interpreters I know that supports Befunge-96 and -97, and I've used it a couple of times on PPCG.

Easier to find if anyone is looking for it.

I'm just going to leave this here: Quadrefunge-97 Hello World.

@Unihedron Another option might be yoob, but it also doesn't have the features you're looking for. Just a basic text editor and a debugger that lets you step through code.

I didn't invent the language. It is what it is.

Although maybe the esolang room (whatever it's called) may be a better place for that.

I'm not exactly an expert on the subject, but if anyone wants to know more, I'll do my best to answer any questions you might have.

For those of you that were asking earlier about how the other dimensions worked in Funge-97, this is a short sample of Quadrefunge-97 code that demonstrates the basic concepts: Try it online!

So I think I'm going to go now. Goodnight everyone.

Case in point: I have no idea why I'm still awake.

There are a lot of things I don't know.

And yes, SE chat has a kick feature. And some kind of ban I think.

They're UTC for me, but I would have thought they're just your local timezone.

That's right. Blame Canada.

Maybe that part of the country has been invaded by the Queen and she just declared it to be UK time there.

Interesting. Never really thought of it as spanning that wide an area.

And Wikipedia also lists the Azores.

I was just going to say, it looks like Greenland too.