View Issue Details

IDProjectCategoryView StatusLast Update
0033802LazarusIDEpublic2020-04-13 18:27
ReporterMartin Friebe Assigned To 
Status newResolutionopen 
Platform64bit IntelOSwin 10 
Product Version1.9 (SVN) 
Summary0033802: IDE "Messages" window does not deal with warnigs from generics during specialization
DescriptionWhen you specialize a generic, fpc may give hints or warnings with the source filename where the generic was declared.

If you specialize the generic, and the unit of definition is in a different package, then the message window will not recognize this.

- You can not double click the message "file xxx not found" (even though xxx seems to be correct)
- If it is a hint, and the source already has {%H}, the hint still shows
TagsNo tags attached.
Fixed in Revision
Attached Files


related to 0036912 feedback Linker errors are not always displayed in the 'Messages' widget 


Mattias Gaertner

2018-05-29 21:38

manager   ~0108575

Can you provide an example?

Martin Friebe

2018-05-31 10:50

manager   ~0108606

Compile components\lazutils\test\TestLazStorageMem.lpi (with fpc 3.0.4)

Within the file testlazstoragememcase1.pas you get:
lazlistclasses.pas(1318,71) Hint: Mixing signed expressions and longwords gives a 64bit result
lazlistclasses.pas(774,8) Warning: Local variable "NewMem" does not seem to be initialized

double click them (single click, if your settings for jump to messages are single click)

Both locations already have a {%H}.
And when you compile the unit in LazUtils the %H works and suppresses the hints

Issue History

Date Modified Username Field Change
2018-05-29 21:26 Martin Friebe New Issue
2018-05-29 21:38 Mattias Gaertner Note Added: 0108575
2018-05-31 10:42 Martin Friebe Summary IDE "Messages" window does not dear with warnigs from generics during specialization => IDE "Messages" window does not deal with warnigs from generics during specialization
2018-05-31 10:50 Martin Friebe Note Added: 0108606
2020-04-13 18:27 Juha Manninen Relationship added related to 0036912