> On Sep 27, 2022, at 5:31 PM, Ondrej Pokorny via fpc-pascal
> wrote:
>
> published
> property MyEnumOrd: Integer read GetMyEnumOrd write SetEnumOrd; //
> gets/sets MyEnum as ordinal value
Yeah I guess that work also albeit with some boiler plate. Thanks.
Regards,
Ryan Joseph
__
> On Sep 27, 2022, at 5:19 PM, Pierre Muller via fpc-pascal
> wrote:
>
> TDiagnosticSeverity = ( NoError { will be 0},
> Error {will stay equal to 1},
> Warning {will stay equal to 2},
> Information {will stay equal to
Am 27.09.2022 um 11:22 schrieb Hairy Pixels via fpc-pascal:
On Sep 27, 2022, at 4:17 PM, Marco van de Voort via fpc-pascal
wrote:
3.2.2 compiles without warnings, 3.3.1 (i386-win32 from 17 sept:)
ptt.pp(14,44) Warning: This property will not be published
Possibly enums with assigned values
Le 27/09/2022 à 11:22, Hairy Pixels via fpc-pascal a écrit :
On Sep 27, 2022, at 4:17 PM, Marco van de Voort via fpc-pascal
wrote:
3.2.2 compiles without warnings, 3.3.1 (i386-win32 from 17 sept:)
ptt.pp(14,44) Warning: This property will not be published
Possibly enums with assigned v
> On Sep 27, 2022, at 4:17 PM, Marco van de Voort via fpc-pascal
> wrote:
>
> 3.2.2 compiles without warnings, 3.3.1 (i386-win32 from 17 sept:)
>
> ptt.pp(14,44) Warning: This property will not be published
>
> Possibly enums with assigned values (which can have gaps) are not safe to
> pub
On 27-9-2022 11:14, Hairy Pixels via fpc-pascal wrote:
I just tried to build a lazarus project using 3.3.1/ppca64 and I’m getting an
error that an enum can’t be published. This was working on 3.2.2/ppcx64 so what
changed?
===
lazbuild ./pasls.lpi --widgets
I just tried to build a lazarus project using 3.3.1/ppca64 and I’m getting an
error that an enum can’t be published. This was working on 3.2.2/ppcx64 so what
changed?
===
lazbuild ./pasls.lpi --widgetset=cocoa
--compiler=/usr/local/lib/fpc/3.3.1/ppca64 --cpu
