ntext
would be something separate and I think we already have that, don't we?
>
> Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
>
> From: Cesar Garcia
> Sent: Saturday, February 4, 2023 6:47:54 PM
> To: dev@plc4x.apache.org
as the Encoding and ByteOrder. Things like the parser
arguments we should probably keep the way they are.
Chris
From: Łukasz Dywicki
Date: Monday, 6. February 2023 at 12:21
To: dev@plc4x.apache.org
Subject: Re: [DISCUSS] Generally move to using "Context" objects inside our
generat
eparate and I think we already have that, don't we?
Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
From: Cesar Garcia
Sent: Saturday, February 4, 2023 6:47:54 PM
To: dev@plc4x.apache.org
Subject: Re: [DISCUSS] Generally move to using "C
4, 2023 6:47:54 PM
To: dev@plc4x.apache.org
Subject: Re: [DISCUSS] Generally move to using "Context" objects inside our
generated code?
+1, If there's a way to get the driver's context, something like
"PlcDriver.getContext()", and pass pipe information, interesti
+1, If there's a way to get the driver's context, something like
"PlcDriver.getContext()", and pass pipe information, interesting.
El sáb, 4 feb 2023 a las 6:18, Christofer Dutz ()
escribió:
> Hi all,
>
> recently I have been working on supporting dynamic tags like “_itemCount”,
> “_curItem” and
pache.org
> Date: February 4, 2023 at 05:18:59
> To: dev@plc4x.apache.org
> Subject: [DISCUSS] Generally move to using "Context" objects inside our
> generated code?
>
> Hi all,
>
> recently I have been working on supporting dynamic tags like “_itemCount”,
> “_cu
Any DSL at some point will consider stack / call / variable contexts.
This seems reasonable.
From: Christofer Dutz
Reply: dev@plc4x.apache.org
Date: February 4, 2023 at 05:18:59
To: dev@plc4x.apache.org
Subject: [DISCUSS] Generally move to using "Context" objects inside our
gene
Hi all,
recently I have been working on supporting dynamic tags like “_itemCount”,
“_curItem” and “_lastItem” in array elements.
In java I used ThreadLocals for this as it felt like a Java-Native way and it
wouldn’t blow up the signatures of our Parser, Serializer and GetLengthInXYZ
methods.
