Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect delta for south/north #5

Closed
bbernardoni opened this issue Jun 21, 2017 · 2 comments
Closed

Incorrect delta for south/north #5

bbernardoni opened this issue Jun 21, 2017 · 2 comments

Comments

@bbernardoni
Copy link

South and North seem to be labeled with incorrect delta values (found here).

Everywhere else seems to indicate south is (0,1) and north is (0,-1).

@cpressey
Copy link
Member

Congratulations! You found a 19-year-old error in the spec.

I can tell you exactly why this is, too. When just starting on the design of Funge-98, I had it in my mind that it would be nice if its co-ordinate system matched the co-ordinate plane commonly used in mathematics. In this, the co-ordinates on the y-axis increase as you move up the page ("north").

But that proved to be an extremely unpopular choice, with most voices on the mailing list expressing a strong preference for retaining the orientation used by Befunge-93, (which matched the one commonly used in early computer graphics,) where y co-ordinates increases as you move down the page.

(You can find a comparison of these two, with some (not totally accurate, but still useful) context, on this page: Introduction to Graphics.)

I conceded to the popular opinion in this case and edited the spec to change the orientation everywhere (including the definition of North and South). Except, of course, I missed a spot, as you have pointed out.

(Thankfully, it seems to not have confused anyone, as the number of other places, in the spec and in written programs, where it is clear that bigger y = south, smaller y = north, has probably overwhelmed this one statement, to the point where it was hard to even spot.)

I'm currently compiling an ERRATA document to accompany the spec, and will mention this error in that document.

Thanks!

@cpressey
Copy link
Member

This error has been listed in the ERRATA document, which has now been released. Thank you for your report. Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants