Michael Van Canneyt via fpc-pascal said on Wed, 11 Oct 2023 08:27:35
+0200 (CEST)
>On Tue, 10 Oct 2023, Steve Litt via fpc-pascal wrote:
>
>> What is webasssembly?
>
>A bytecode format (similar to what is used in Java and C# runtimes)
>which is an open standard and which runs in all major browse
On 11/10/2023 16:46, Adriaan van Os via fpc-pascal wrote:
I don't see any use in allowing or disallowing something. And with the
current design, it is, as I said, impossible, without macros, to
compile the same code with {$M+} and {$M-}.
Use $IfOpt instead of macros?
{$IfOpt M+} published {$E
On Wed, 11 Oct 2023, Adriaan van Os via fpc-pascal wrote:
Michael Van Canneyt via fpc-pascal wrote:
$M controls the inclusion of RTTI, i.e. it allows or disallows the use of
the published section.
No more, no less.
I don't see any use in allowing or disallowing something. And with the
c
Michael Van Canneyt via fpc-pascal wrote:
$M controls the inclusion of RTTI, i.e. it allows or disallows the use
of the published section.
No more, no less.
I don't see any use in allowing or disallowing something. And with the current design, it is, as I
said, impossible, without macros, to
On Wed, 11 Oct 2023, Adriaan van Os via fpc-pascal wrote:
Sven Barth via fpc-pascal wrote:
Ah, yes, only classes and interfaces can be used for published fields. For
properties anything is allowed.
However, what makes the whole thing unuseable is that with {$M-} the compiler
doesn't acc
Sven Barth via fpc-pascal wrote:
Ah, yes, only classes and interfaces can be used for published fields.
For properties anything is allowed.
However, what makes the whole thing unuseable is that with {$M-} the compiler doesn't accept
"published". So, without using macros, the same source code
