Where is the implementation of WriteLn()

[marcov]

Personally, I like the writeln-to-stream construct. The concatenation syntax  (and required conversion calls like inttostr and padding) is a nuisance.

[rvk]

Personally, I like the writeln-to-stream construct. The concatenation syntax  (and required conversion calls like inttostr and padding) is a nuisance.

Me too. But you don't need inttostr and padding if you use the format function. That's the only upside of converting it. With format and it's variable replacement it is sometimes more readable. Sometimes

[Thaddy]

Note headconv (by Bob Swart, a.k.a. drBob) has always been open source. The only difference with the JEDI version is that that version is open source licensed...whereas the original is just copyrighted freeware.
Note 2: cpp-E -> h2paspp-> h2pas gives better results in most cases.

In general I use either the new formatting helpers (see my example, this is delphi compatible) or indeed writestr and lately refrain from actual classic formatting functions in newer code. Dunno why, so don't ask 

[marcov]

Personally, I like the writeln-to-stream construct. The concatenation syntax  (and required conversion calls like inttostr and padding) is a nuisance.

Me too. But you don't need inttostr and padding if you use the format function. That's the only upside of converting it. With format and it's variable replacement it is sometimes more readable. Sometimes

I like interpretive I/O even less than concatenation, so I mostly use format only for locale strings and occasional formatting numbers in the way writeln doesn't allow.

[Thaddy]

But you don't need inttostr and padding if you use the format function. That's the only upside of converting it. With format and it's variable replacement it is sometimes more readable. Sometimes

Hm. that's probably why I use the type helpers for simple types so much: I like boxing (not everybody does, it is an acquired taste, like Brussels sprouts), especially the series of ToString overloads.