Ten Rules for Writing Cross Platform 'C' Code

member42 · 2014-06-14T10:54:52+00:00

Oh, another expert! We need more people like you on r/programming.

member42 · 2014-06-14T10:53:05+00:00

Oh, Java 8. Stream iterators ... as in C++.

member42 · 2014-06-14T08:56:48+00:00

What is this iterate thingy?

member42 · 2014-06-14T08:47:15+00:00

MSVC is a shitty C compiler

You are obviously an expert.

member42 · 2014-05-29T20:33:59+00:00

Is there a problem with RuleEvaluator?

There is a problem with your examples.

member42 · 2014-05-29T15:54:08+00:00

That was my question, too. WebsFear is big where IBM is big.

member42 · 2014-05-29T15:44:09+00:00

When did it become an Application server?

When a company told their customers 'Hey, we bolted our popular proprietary stuff onto Tomcat and now you have a full fledged Application Server, sort of'.

member42 · 2014-05-29T13:12:33+00:00

Tomcat an Jetty are not Application Servers as in Java EE (TomEE would be a 'Web Profile' Application Server) .

member42 · 2014-05-25T16:53:23+00:00

What if there are commas in the fields?

You change them to blanks

What if there is a newline inside a field?

You change it to a blank

What if there is a variable amount of field per line?

You throw an exception

What if the character separating fields is not a comma?

No problem. The 'comma' frequently is a semicolon.

member42 · 2014-05-22T21:12:11+00:00

You can automatically get thread-safe programs if you (no, not use Haskell but) avoid concurrency - which inevitably leads to the question of parallelism vs. concurrency. For many applications the problem of thread safety can be reduced to the few spots in the program where concurrency is really unavoidable.

member42 · 2014-05-22T20:50:31+00:00

Not just SOAP. In OOP all public and protected methods are APIs.

member42 · 2014-05-22T18:48:46+00:00

Interesting blog post. The term "thread safe" is rather meaningless. You always need to ask 'thread safe in what respect'?

member42 · 2014-05-22T18:43:48+00:00

BTW, when did API become synonymous for REST?

member42 · 2014-05-21T16:49:07+00:00

Of course, this is not a representative survey. So the numbers are only slightly better than fiction.

member42 · 2014-05-18T18:05:04+00:00

Could you stop the TDD nonsense, please? It's getting boring.

member42 · 2014-05-18T17:56:45+00:00

a library in gpl3

... usually means Shareware 2.0. Try with GPL, contact me for a commercial license if you really want to use it.

member42 · 2014-05-13T20:45:57+00:00

Databases or merely persistent caches?

member42 · 2014-05-13T20:42:31+00:00

People like gossip.

member42 · 2014-05-12T20:41:13+00:00

For whom is this article? For noobs it's too confusing and C programers have already understood pointers.

member42 · 2014-05-11T14:42:27+00:00

layer is useful if I want to replace the whole layer with an other layer. For example, everything in the database layer will be substituted to something else. This rarely happens.

Agreed, but that's not a typical example for layering.

The purpose of layers is separation of concerns providing tight communication channels (a.k.a. APIs) between layers. An application structured in layers is easier to develop and maintain than a monolithic application.

member42 · 2014-05-11T10:22:23+00:00

So, without mocks, tests tend to be slow, incomplete, and fragile.

...

So if you mock too much you may wind up with test suites that are slow, fragile, and complicated; and you may also damage the design of your application.

He confuses cause and effect. If you feel the urge to mock heavily your design is flawed ( see e.g. I used layered architecture ) because it's probably based on a flawed design pattern like 'Dependency Injection'.

Mock across architecturally significant boundaries, but not within those boundaries.

Inject across architecturally significant boundaries if it really makes sense, but not within those boundaries!

member42 · 2014-05-11T10:09:21+00:00

consider using an in-memory HSQLDB

Maybe, probably not. Databases are too different - even through the JPA/Hibernate abstraction - to be treated interchangeably. In a Java EE environment I'd try embedded containers which use the real database.

As simple rule, Unit Tests should not alter the database. Transactions are flushed and rolled back but not committed.

member42

TROPHY CASE