Re: [fpc-pascal] Rest in peace Martin Schreiber

"No man is an island, entire of itself; every man is a piece of the continent, a part of the main; if a clod be washed away by the sea, Europe is the less, as well as if a promontory were, as well as if a manor of thy friends or of thine own were; any man's death

Re: [fpc-pascal] SetLength warnings - request

Hi, even if there's closed issue https://bugs.freepascal.org/view.php?id=34169 I would like to ask if it can be reconsidered. The subject is that SetLength now gives warning: Variable "dynamic array" of a managed type does not seem to be initialized in 3.3.1 and 3.1.1 while it doesn't give

[fpc-pascal] inlining functions depending on implementation only functions

Hi, after updating from fpc 3.1 to fpc 3.3, I am getting a lot of "function was not inlined" warnings, e.g. when an inline function depends on a function not declared in the interface part like: unit inlinetest; {$mode objfpc}{$H+} interface uses   Classes, SysUtils; function strContains

Re: [fpc-pascal] inlining functions depending on implementation only functions

On 12/29/18 9:16 AM, Benito van der Zander wrote: Fpc 3.1 did not show any warning in this case (although now that I investigate it, fpc 3.1 also did not seem to inline it despite not showing the warning) i think, but am not totally sure, that the addition of the warning is a recently added fe

Re: [fpc-pascal] SetLength warnings - request

On 29.12.2018 16:19, Benito van der Zander wrote: Hi, even if there's closed issue https://bugs.freepascal.org/view.php?id=34169 I would like to ask if it can be reconsidered. The subject is that SetLength now gives warning: Variable "dynamic array" of a managed type does not seem to be init

Re: [fpc-pascal] inlining functions depending on implementation only functions

Am Sa., 29. Dez. 2018, 15:23 hat Benito van der Zander geschrieben: > Hi, > > after updating from fpc 3.1 to fpc 3.3, I am getting a lot of "function > was not inlined" warnings, e.g. when an inline function depends on a > function not declared in the interface part like: > > unit inlinetest; > >

Re: [fpc-pascal] SetLength warnings - request

Surely the point of a hint/warning is to point out a potential issue that the programmer may wish to correct. It should therefore be possible to change your code such a way that the hint/warning can be resolved so that it is no longer printed. This should not entail redundant or unnecessary code.

Re: [fpc-pascal] SetLength warnings - request

On 2018-12-29 22:00, Derek Edson wrote: Would it not be simpler to have the compiler initialize all dynamic array variables to nil, like for string variables, which should prevent the uninitialized warning/hint without requiring special treatment for handling the SetLength function. It does