View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0035977||Packages||Packages||public||2019-08-17 15:25||2019-08-18 23:40|
|Product Version||2.0.4||Product Build||chronolog_package 0.1|
|Target Version||Fixed in Version|
|Summary||0035977: a ; out of place|
|Description||package do not compile at end|
|Steps To Reproduce||Compile package chronolog_package 0.1:|
|Additional Information||package chronolog_package 0.1: Codice di uscita 1, Errori: 1, suggerimenti: 1|
cpu.pas(137,24) Note: Values in enumeration types have to be ascending
cpu.pas(372,30) Fatal: Syntax error, "identifier" expected but ";" found
remove the ; at line end
as lazarus redownload package, it comes back
|Tags||No tags attached.|
|Fixed in Revision|
||main package is LuiPack|
||AFAIK this is not part of Lazarus?|
The luipack is maintained by Luiz, and he is developer here; so, I think it is ok to report the issue here.
However, I cannot reproduce the issue on my system (Win 10 (64 bit), Laz trunk, fpc 3.2, 32 bit):
- I installed the chonolog_package via Online-Package-Manager (well: it is a runtime package, it is only compiled, not really "installed") - it has version 0.1 as noted in the report.
--> No problem during compilation
Looking into unit cpu.pas, near line 372 I see:
This is perfectly correct as long as the symbols OS_WINDOWS or OS_UNIX are defined (and the outer conditions are met). If, for example, you are on a Mac, however, where these symbols are not defined, there is indeed a vagabonding semicolon as reported.
But I doubt if this is a real issue. It is just a consequence of the fact that the chronolog_package seems to work only for Windows, *nix as well as OS/2 and DOS systems (for the latter ones the uses clause is bypassed).
It is a bit mysterious, though, because your report header says that your OS is Windows.
|2019-08-17 15:25||bob||New Issue|
|2019-08-17 15:28||bob||Note Added: 0117717|
|2019-08-17 15:51||Bart Broersma||Note Added: 0117718|
|2019-08-18 22:44||wp||Note Added: 0117731|
|2019-08-18 22:45||wp||Note Edited: 0117731||View Revisions|
|2019-08-18 22:47||wp||Note Edited: 0117731||View Revisions|
|2019-08-18 23:40||wp||Note Edited: 0117731||View Revisions|