Hi Nikolai,
I don't even know the testsuite URL myself - I just run the regression
tests as found under "fpc/tests", which is fairly public given there's a
readme file there explaining how to run them.
I guess I'm a little confused because when I try to compile the tests
manually from the comman
I’ve looked into this more today and I don’t see how we can get around needing
a typesym for specializations.
For example:
generic procedure DoThis(msg: T);
begin
end;
var
a: array of char;
begin
DoThis(a);
Is going to specialize as DoThis(a). “array of char” is (for
lack of
Hi,
02.03.2019 19:59, J. Gareth Moreton:
It might need double-checking, but I'm getting a couple of regressions
on the trunk for i386-win32 and x86_64-win64:
Failed, compilation successful webtbf/tw4893d.pp 2018/12/06 07:01:14
Failed, compilation successful webtbf/tw4893e.pp 2018/12/06 07:01:14
It might need double-checking, but I'm getting a couple of regressions on
the trunk for i386-win32 and x86_64-win64:
Failed, compilation successful webtbf/tw4893d.pp 2018/12/06 07:01:14
Failed, compilation successful webtbf/tw4893e.pp 2018/12/06 07:01:14
Both these tests seem to be label/goto
On Sat, Mar 2, 2019 at 5:53 PM Bart wrote:
> As a side note: I now have several patches for the registry in the
> bugtracker, and it gets increasingly difficult to make new patches for
> each issue if the "previous" (as in: the ones I made earlier) don't
> get applied.
Applying the patch for thi
On Sat, Mar 2, 2019 at 3:48 PM Joost van der Sluis wrote:
> The utf8encode should go, just like the utf8decode's that we fixed already.
Shall I post a patch in the bugtracker?
If so: instead of
SomeAnsiString := UTf8Encode(SomeUnicodeString) do I make it an
implicit conversion (SomeAnsiString :=
Op 01-03-19 om 22:19 schreef Bart:
On Tue, Feb 26, 2019 at 10:49 AM Marco van de Voort
wrote:
If I look into e.g. registry.pp, the only use of utf8encode there is
like this:
var s : string;
u:unicodestring;
s:=utf8encode(u);
which, IF lazarus is used in the default utf8 mode is e
