Hacker News new | past | comments | ask | show | jobs | submit login

My little short gem from being forced to take a course on ABAP (the SAP "programming language") at Uni:

If you have an error in your program, your editor crashes. You have to start a new editor instance by wrangling through a dozen submenus and entering cryptic commands.

The guy overseeing the course said "Yeah, just open a few backup instances of the editor beforehand."




What's actually happening there is you are executing the program directly from your editor, in the same work process. So if you get a runtime error, then you get the stack trace (dump) and you have lost your whole context so you are back to the menu.

Just run the program in another session.


I'll try to remember that the next time I'm programming ABAP (hopefully never)

The point is that even the instructor didn't know how solve the problem and that the default behavior is not exactly developer friendly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: