burstmode

Results of code review of false.c:

* Use of undocumented magic numbers (1)

* No use of getter/setter pattern

* Inflexible design (datatype of result is fixed, no template pattern implemented)

* Manual memory management (no garbage collection used)

* No infrastructure for automated testing included

* No unit tests available

* Code has not changed for Years (code smell!); Probable stale code, to be removed in next release.

3 Generations of PCBs and still no RTC onboard...

Great ! Now the GIMP team will use this opportunity to create their own version of a "domain". I will look & work mostly like all other domains, but just mostly. Like you will not be allowed to directy save a change to its structure...

Yeah, it's alway funny to see the reaction of fresh-from-the-mill CS-academics when they have to code in an MISRA regulated project for the first time. Around half of them quits after a month because they are unable to write 100 lines of working code without some babysitter (aka. garbage collector) cleaning up behind them.

C++ started out as a great 'next generation C', but in the last years it became a playfield for CS-academics, just adding one useless esotheric feature after each other.

At least every 2nd C programmer working on a non-unix platform has been burned by this at least once. It's like a 10ft deep pothole on Broadway that won't get fixed because traditionalists see it as a 'national monument'.

Well, that comes from the Garbage Collector, cleaning after all the programmers to lazy think about resource usage. But hey, never mention this when together with Java-developers, because saying something critical about garbage collection ist almost as bad as denying global warming.

Why so many people hate Java ? Let's start with the fact that it installs an auto-update system that tries everthing it can to trick you into installing adware (ask-bar).

Well, if there are people analyzing exploits then there must also be people creating them... :->

Telling anybody to use vi at all is pretty hilarious.

then they cast to void()

If uint16_t really is a signed 15bit value under VS2013, somebody in the compiler development department has a great sense of humor.

Yes, mainly because new sword has an auto-grinder welded to it that might start running at any given moment, even if you are in a deathly fight :-)

>What do you do when your error logging code reports a failure? Keep trying to log the same error, or do you begin trying to log the error that you can't log errors anymore?

First you try to fix the problem of the logging system by runnig a reorganisation routine (delete old data,...) or reinit the subsystem. If that does not work AND if logging is a manadatory function of you system you make sure to change into a safe state and inidcate a fatal error state (blinking light, beeper, whatever). If the logging is such an important part of the system surrounding your system it might take further actions on its own and reinit your system (maybe turn your system off and start another logging systen). There is no exit. You never give up.

Great, so now that he explained to us how to use strings for human readable text, the last missing bit is a blogpost telling the author how to choose the colors for letters & background. What's the sense in optimizing string usage when half of the audience can't read the lightgray text on slightly-lighter-gray background ?

I'm sure there is some space left for fancy named design patterns and a template library with lambda support. You know you can't write a website without lambdas, don't you ?

20 years ago, during the peak of the CASE hype, there used to be several others.Borland ObjectVision, IBM VisualAge, Siemens EasyCase were some of them. Problem of all this tools is: It's proven that they don't scale. The sample programms that come with them all look nice and tidy, but god beware if you have to solve some real problem with real error handling. Right now Matlab Simulink&Stateflow (+some kind of code generator) is the only system usable for fingerpainting programms of significant size.

So, what you say is: I don't care to implement an efficient solution, because the CPU cache will fix it anyway. That way of thinking is well known as "The Java way of problem solving" (TM)

just turn off javascript....

SlickEdit

What makes you think that the Iraq & Afghanistan wars will be over in 45 years ?

C++11 itself not theoretical, but the added "improvements" to the language are mostly theoretical. Since adding the template concepts a few years ago, the steering committee has dropped all sense for pragmatic design decisions and replaced it with fashionable-at-the-moment CS-concepts that will not improve your life as a developer in the real world. There is a good reason why most companies limit/prohibit the usage of certain newer C++ features. Using them only adds complexity while not leading to better software (>speed,<size, >maintainability).

>On a slightly related note, a just-in-time compiler with a superb garbage >collector can be more performant in some situations due to its ability to >profile and optimize the code while the application is running.

No Garbage collector can be faster then a programm that produces no garbage at all, because its programmer knew what he was doing.

>For $189, I can slap a 240GB SSD in the machine to make software more >performant. The question you have to ask is: How much optimization can >a senior-level programmer accomplish for $189?

This ist the typical academic way of optimization: Let's write some programm and then throw hardware on it until it runs fast enough. In the real world, ressources are limited. That $189 are needed for each install of your garbage-collected software, not just YOUR personal develoment machine.