On 09 Mar 2013, at 23:46, Vittorio Giovara wrote:
Slightly off topic: http://www.utf8everywhere.org/
Seriously, drop UTF16 support NOW.
No, that's very off-topic. Please don't start discussions like that here, they
don't lead to any useful outcome.
Jonas
FPC mailing lists
Van: Vittorio Giovara vittorio.giov...@gmail.com
On 04/mar/2013, at 16:57, luiz americo pereira camara
luiz...@oi.com.br wrote:
Personally, i don't care much about compilation speed since is
faster
enough (at least for me). I'm more interested in better generated
code. This is were
2013/3/9 Marco van de Voort mar...@stack.nl:
the first problem is that fcl-passrc likes to use OUT for all kinds of
parameters, probably to silence some warnings.
BUT at the same time doesn't assign a value to it in all codepaths (in this
case the visibility checking methods). At the same
In our previous episode, Vincent Snijders said:
So be careful if you use OUT with types that have range limitations. Not
setting the out parameter can make debug tools like gttt difficult.
You found a big in fcp-passrc, because if you have an out parameter,
then the callee has to output
Hi, FPC developers!
I've commited patch to issue 9961 few days ago, and I'd like to ask if
someone could take a look at it? I'm currently analyzing several other
unit-loading issues (10551, 18294) with similar situations (relative
paths, different unit loading order when compiling and loading
On Sun, Mar 10, 2013 at 11:56 AM, Marco van de Voort mar...@stack.nl wrote:
In our previous episode, Vincent Snijders said:
So be careful if you use OUT with types that have range limitations. Not
setting the out parameter can make debug tools like gttt difficult.
You found a big in
On 10.03.2013 20:39, Flávio Etrusco wrote:
On Sun, Mar 10, 2013 at 11:56 AM, Marco van de Voort mar...@stack.nl wrote:
In our previous episode, Vincent Snijders said:
So be careful if you use OUT with types that have range limitations. Not
setting the out parameter can make debug tools like
