I fixed an bug in a Sepples program today!

As it turned out, someone (possibly not me) forgot to put a semicolon after the closing bracket of a class definition in a header file that was included by several other files, and it was shouting three hundred error messages at me about how that it couldn't find an overload for std::basic_string<_Elem, _Traits, _Ax>::append [with _Elem=wchar_t, _Traits=std::char_traits<wchar_t>, _Ax=std::allocator<wchar_t>] and how this and that were inaccessible member variables, and how incomplete type data was against the law, and that default-int was not allowed. Then I had a flash of intuition and fixed it all with a single click of my keyboard.

It felt amazing. I felt amazing. I finally understand why this whole C++ thing still has such a following.

Now change the include order so that the compiler gets stuck in an infinite loop of error messages. I think it was possible to do that with MSVC++.

yeah, 300+ lines of errors is a forgotten semicolon or some shit like that

>>1

That is a syntactic error, not a bug. A bug is runtime error with no obvious cause. The /prog/'s quality has fallen last year. Instead of academic languages master race, /prog/ is now populated by FrozenAnus level C/C++-retards. Even Cudder's x86 decompilation bullshit had higher value.

academic languages master race reporting in.

RWH was written at a time version 6.8 of GHC was being used. 6.8 used base version 3.0.x.x. 6.10.1 already used 4.0.0.0, which introduced many changes. And that's just the jump from 6.8 to 6.10. The current version of GHC is 7.8, and the upcoming 7.10 will change monads significantly (see below).

have fun rewriting your code every 6 months.

meanwhile:

Gofix is a new tool that reduces the amount of effort it takes to update existing code. It reads a program from a source file, looks for uses of old APIs, rewrites them to use the current API, and writes the program back to the file. Not all API changes preserve all the functionality of an old API, so gofix cannot always do a perfect job. When gofix cannot rewrite a use of an old API, it prints a warning giving the file name and line number of the use, so that a developer can examine and rewrite the code. Gofix takes care of the easy, repetitive, tedious changes, so that a developer can focus on the ones that truly merit attention.

>>1
Why did they check in code that could not even compile?

>>6

Because good programs are written for people to read, and only incidentally for machines to execute.

>>7
Good programs should be written for machines to execute.

>>8
Good programs should also be written for daytime telly

>>8
Shalom!

>>9

For a fag break too?

>>4
Academic language individual here. I don't post about programming anymore.

>>1,6-8
Irrelevant. Code that doesn't compile can't be executed by a machine, so it's not a program at all.