A plugin is the more logical route, for the ones that want to remain
libc
free, but want to risk maintainance problems.
Like an fplocale unit, that users can include if they do not want to
use clocale?
Yes, I don't see a problem with that, if the quality is suitable. (read:
Hi,
I never used TList before, so I'm not sure if this is correct.
I constructed a TlcTextCache class that basically stores objects of
type TLcText in a TList.
A TlcText object is create with TLcText.Create(FileName).
My questions:
- I add my TlcText objects to the list by
Hello,
I wanted to port an old program from fpc 1.0.4 (SuSE 7.0) - fpc 2.0.4
(openSuSE 11.0, 32-bit). My program uses ken wright's oCRT, and I have a
version which was extended by ken wright personally with some additional
functions.
It was very surprising that I could compile the main part of
Marco van de Voort wrote:
It is roughly ok. Optionally you can also -dFPC_USE_LIBC to force the system
unit to use libc instead of syscalls, and save a few kb. Note that this is
less frequently tested though.
I wasn't aware of that, and that would actually get me a lot closer to
what I'm
- Original Message -
From: Bart bartjun...@gmail.com
To: FPC-Pascal users discussions fpc-pascal@lists.freepascal.org
Sent: Wednesday, April 01, 2009 10:12 PM
Subject: [fpc-pascal] TList: newbie question
Hi,
I never used TList before, so I'm not sure if this is correct.
I
