Den 02-01-2015 kl. 15:07 skrev Jonas Maebe:
On 02/01/15 14:55, Bart wrote:
On 1/2/15, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
The reason is that by design, FPC-compiled programs for Linux do not
depend on libc and clocale introduces a dependency on libc. It's the
same reason why you have
On 02/01/15 14:55, Bart wrote:
On 1/2/15, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
The reason is that by design, FPC-compiled programs for Linux do not
depend on libc and clocale introduces a dependency on libc. It's the
same reason why you have to use the cthreads unit to get a
On 02/01/15 13:35, Giuliano Colla wrote:
Contrary to what written in docs, DefaultFormatSettings aren't adjusted
to the current locale in Linux at the startup of an application both on
fpc 2.6.4 and on fpc 2.7.1.
Where is this written? At least
On Fri, 2 Jan 2015, Jonas Maebe wrote:
On 02/01/15 14:55, Bart wrote:
On 1/2/15, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
The reason is that by design, FPC-compiled programs for Linux do not
depend on libc and clocale introduces a dependency on libc. It's the
same reason why you have
In our previous episode, Jonas Maebe said:
After just having spent 2 days debugging an issue in fcl-res that could
have been avoided by just using the assembler instead of by
reimplementing object writers from scratch,
I do like the object writers mostly from a support viewpoint. The FPC
Il 02/01/2015 13:47, Jonas Maebe ha scritto:
On 02/01/15 13:35, Giuliano Colla wrote:
Contrary to what written in docs, DefaultFormatSettings aren't adjusted
to the current locale in Linux at the startup of an application both on
fpc 2.6.4 and on fpc 2.7.1.
Where is this written? At least
Contrary to what written in docs, DefaultFormatSettings aren't adjusted
to the current locale in Linux at the startup of an application both on
fpc 2.6.4 and on fpc 2.7.1.
One is forced to explicitly add clocale in the uses section of the
application, in order to get the proper locale settings.
On 1/2/15, Jonas Maebe jonas.ma...@elis.ugent.be wrote:
The reason is that by design, FPC-compiled programs for Linux do not
depend on libc and clocale introduces a dependency on libc. It's the
same reason why you have to use the cthreads unit to get a functional
thread manager under Linux.
On 02/01/15 15:59, Jeppe Græsdal Johansen wrote:
Den 02-01-2015 kl. 15:07 skrev Jonas Maebe:
After just having spent 2 days debugging an issue in fcl-res that could
have been avoided by just using the assembler instead of by
reimplementing object writers from scratch, I'm even more
Am 02.01.2015 um 16:43 schrieb Jonas Maebe:
On 02/01/15 15:59, Jeppe Græsdal Johansen wrote:
Den 02-01-2015 kl. 15:07 skrev Jonas Maebe:
After just having spent 2 days debugging an issue in fcl-res that could
have been avoided by just using the assembler instead of by
reimplementing object
Florian Klämpfl wrote:
Am 02.01.2015 um 16:43 schrieb Jonas Maebe:
On 02/01/15 15:59, Jeppe Græsdal Johansen wrote:
Den 02-01-2015 kl. 15:07 skrev Jonas Maebe:
After just having spent 2 days debugging an issue in fcl-res that could
have been avoided by just using the assembler instead of by
Michael Van Canneyt wrote:
On Fri, 2 Jan 2015, Jonas Maebe wrote:
in my conviction that it is a mistake trying to implement and
reimplement everything just to make cross-compiling somewhat easier, or
to avoid libc version compatibility problems on Linux that were common
15 years ago.
I will
12 matches
Mail list logo
