Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On Mon, 11 Jan 2016 14:24:40 +0100 "John Landmesser" wrote: >[...] > Kompiliere Package IDEIntf 1.0: Exit code 1, Fehler: 4, Hinweise: 1 > projectintf.pas(708,14) Error: Identifier not found "RawByteString" Fixed. Mattias -- ___

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On Mon, 11 Jan 2016 07:00:59 -0700 (MST) leledumbo wrote: > > Isn't it possible anymore to compile svn Lazarus with fc 2.6.4 ?? > > No. Latest stable is the only one that's supported, latest stable is 3.0.0. FPC 3.0.0 is still fresh. We should try to give users

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

> Isn't it possible anymore to compile svn Lazarus with fc 2.6.4 ?? No. Latest stable is the only one that's supported, latest stable is 3.0.0. -- View this message in context:

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On Mon, Jan 11, 2016 at 4:00 PM, leledumbo wrote: >> Isn't it possible anymore to compile svn Lazarus with fc 2.6.4 ?? > > No. Latest stable is the only one that's supported, latest stable is 3.0.0. Actually we plan to keep Lazarus compilable with FPC 2.6.4 for some

[Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

i get this error message if i try to compile    Lazarus 1.7 r50846 FPC 2.6.4 i386-win32-win32/win64 ( last working version, December 2015 )   Message: Kompiliere Package SynEdit 1.0: Abgebrochen, Warnungen: 1, Hinweise: 2 synedithighlighterfoldbase.pas(1168,43) Hint: Mixing signed

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On Mon, 11 Jan 2016 10:46:00 -0500 Dmitry Boyarintsev wrote: > On Mon, Jan 11, 2016 at 10:32 AM, Mattias Gaertner < > nc-gaert...@netcologne.de> wrote: > > > There is no overload. There is only one definition: > > > > {$define PathStr:=RawByteString} > > > why not >

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

Am 11.01.2016 um 15:23 schrieb Mattias Gaertner: On Mon, 11 Jan 2016 14:24:40 +0100 "John Landmesser" wrote: [...] Kompiliere Package IDEIntf 1.0: Exit code 1, Fehler: 4, Hinweise: 1 projectintf.pas(708,14) Error: Identifier not found "RawByteString" Fixed. Mattias --

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On 11.01.2016 16:32, Mattias Gaertner wrote: On Mon, 11 Jan 2016 16:13:49 +0100 Ondrej Pokorny wrote: I think it fails to find exact overloads. There is no overload. There is only one definition: {$define PathStr:=RawByteString} function ChangeFileExt(const FileName,

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On Mon, 11 Jan 2016 17:42:23 +0100 Ondrej Pokorny wrote: >[...] > finah.inc is loaded twice with different PathStr macro so there are > effectively 2 overloaded ChangeFileExt. You are right. > The issue can be easily reproduced (try to complete X): > > function

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On Mon, 11 Jan 2016, Dmitry Boyarintsev wrote: On Mon, Jan 11, 2016 at 10:32 AM, Mattias Gaertner < nc-gaert...@netcologne.de> wrote: There is no overload. There is only one definition: {$define PathStr:=RawByteString} why not type PathStr= RawByteString; ? Poor mans generics,

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On 11.01.2016 15:22, Mattias Gaertner wrote: In this particular case RawByteString is not needed and not intended. It probably was created by auto completion of xIconFiles|:=ChangeFileExt(); Correct. It wasn't definitely intended. I'll be more careful when using Code Completion. On

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On Mon, 11 Jan 2016 16:13:49 +0100 Ondrej Pokorny wrote: >[...] > > xIconFiles|:=ChangeFileExt(); >[...] > > Code completion needs a heuristic when to use String (or maybe > > AnsiString) instead of RawByteString. > > I think it fails to find exact overloads. There is no

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On Mon, Jan 11, 2016 at 10:32 AM, Mattias Gaertner < nc-gaert...@netcologne.de> wrote: > There is no overload. There is only one definition: > > {$define PathStr:=RawByteString} > why not type PathStr= RawByteString; ? thanks, Dmitry -- ___ Lazarus

Re: [Lazarus] Lazarus trunc does not compile with fpc 2.6.4 Win32

On 11.01.2016 18:18, Mattias Gaertner wrote: I'm aware. Codetools have only three states: exact, compatible and incompatible. But in case of RawByteString and UnicodeString one "compatible" is not enough. This is somehow not entirely correct (I haven't checked why). The integer example I gave