useful, and not entirely inaccurate! Particularly the
part about performance. If a programmer knows exactly what each
exception statement inserts in the code, that should help in deciding
when to worry about the performance, and when to embrace the conveni
"Int128Rec", which is a record type for
holding a 128-bit int. Looks like it's currently used only by
InterlockedCompareExchange128. Someone brave could expand upon that.
~Kirinn
On 08/07/2018 03:11 PM, J. Gareth Moreton wrote:
I think there was talk at one point about implementi
icitly a block. All examples in the documentation show only a single
statement in any else clause, or an explicit begin-end block.
Is this expected behavior? If yes, the reference guide (13.2.2) would
benefit from mentioning this.
~Kirinn
___
fpc-devel maillist
PM, Sven Barth via fpc-devel wrote:
Am 19.09.2019 um 21:07 schrieb Kirinn:
I've stumbled on a situation where a case statement compiles when I
wouldn't expect it to. I would expect the below code to produce a
compile error:
program test;
var i : byte = 5;
begin
that arrays of const are very powerful, and work
beautifully, except for lacking support for one of the most common
variable types. And because an array of const is a compiler-level
construct, I can't even override it. This feels frustrating. :(
~Kirinn
an't vouch for other platforms.
~Kirinn
On 8/22/20 1:44 AM, Martin via fpc-devel wrote:
I am tracing a race condition in lazCollections TLazThreadedQueue
on win-64
What is supposed to happen in the following case:
2 or more threads are waiting on the some event
RTLeventWaitFor(Uniqu
oth a
black and a white background.
I hope a new FPC release happens sooner rather than later; colored
output is really nice to have.
~Kirinn
On 11/22/20 2:59 PM, J. Gareth Moreton via fpc-devel wrote:
Hi everyone,
This might be me being a little bit picky, but I noticed the new
colouring s
it was not clear what to do about it; which tests are
expected to be failing, which are dealbreakers, etc. Should the test
step offer more detail on how to react to or report test suite results?
~Kirinn
___
fpc-devel maillist - fpc-devel@lists.freepasca
happening already in 3.2.0, so not a
regression. I don't see a bug for this yet, so I'll try to come up with
a minimal reproducible. We'll need to warn users about this if it can't
be fixed for 3.2.2.
~Kirinn
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
d of game programmer, I don't think I've ever used a case something
mod something. I'm not sure in what situation this construct would be
useful...
~Kirinn
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
sed change? And, what min_int is of course
depends on whether targeting a 32-bit or 64-bit system, so best check both
cases.
~Kirinn
On Mon, 15 May 2023 17:21:30 +0100
"J. Gareth Moreton via fpc-devel" wrote:
> I made a merge request that removes the comparison against -1.
> x86_64
n that, to set
minds at ease. Thank you for this hard work!
~Kirinn
On Mon, 24 Jul 2023 21:49:39 +0200 (CEST)
Michael Van Canneyt via fpc-devel wrote:
> Hello,
>
> I have just completed phase one of the "Unicode RTL" effort.
>
> The 'Unicode RTL' is an
12 matches
Mail list logo
