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
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
> 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
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
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
> 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
> 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
__
So I got the project building after changing the enums but now after running
the server breaks after sending the first request and I get the error "'No
class "initialize" with method "initialize" was found”.
Here’s a little snippet of the messages I got back but I don’t even know where
to start
El 28/9/22 a les 3:06, Hairy Pixels via fpc-pascal ha escrit:
:: <~~ pascal-language-server 6: {'message': 'Parameters must be passed in an
object or an array.', 'code': -32602}
Maybe related to this?
https://lists.freepascal.org/pipermail/pas2js/2022-September/00.html
(though I'm getti
> On Sep 28, 2022, at 1:34 PM, Luca Olivetti via fpc-pascal
> wrote:
>
> Maybe related to this?
>
> https://lists.freepascal.org/pipermail/pas2js/2022-September/00.html
The question then is did they change something in 3.3.1 in regards to how
parameters can be sent? The error "Parameter
10 matches
Mail list logo