Replies: 1 comment
-
After Overall to summarize, this release doesn't bring any new features other than event triggered frames, really it's only meant to keep the maintainability of the library up and it's just the beginning of upcoming changes that will make it more usable in scenarios such as code generation or communication. Up next is the refactoring of signal encoding according to changes in |
Beta Was this translation helpful? Give feedback.
-
Added
LinVersion
class was added that allows better version handling than the previous floating pointvalues
LinEventTriggeredFrame
objectsChanged
LinFrame
class intoLinUnconditionalFrame
Fixed
None
when event triggered frames were referencedDeprecated
parseLDF
,parseLDFtoDict
,parseComments
were deprecated in favor of the same methods with asnake case signature
LDF::frame(x)
,LDF::signal(x)
,LDF::slave(x)
were deprecated, they were replaced with propergetters but those contracts are slightly different
It's recommended to replace the deprecated functions as they will be removed in
1.0.0
, most ofthem have drop in replacements.
Migration guide for 0.10.0
Imports and classes
A few modules were reorganized, this might cause certain
import
statements to be broken, importsthat only use the
ldfparser
package are backwards compatiblePreviously
LinFrame
represented unconditional frames and was used to encode and decode frames,this was changed in order to support the other frame types later.
LinFrame
now only containsthe most basic properties, name and identifier, while the rest has been transferred out into
LinUnconditionalFrame
andLinEventTriggeredFrame
. This change should only affect scripts thatdirectly reference the
LinFrame
class, when using queries through theLDF
objects the behavioris identical.
Dictionary object
protocol_version
andlanguage_version
were changed to be of string type, the previous floatingpoint values were good for comparing versions but it's overall problematic due to precision issues,
if you still need floating point values then you must convert them in your scripts
LDF object
but everything else had to be accessed through the member fields. This is changed in
0.10.0
inorder to allow a better deprecation process in the future.
_
to mark them as internal, they should not be accesseddirectly
ldf.signals
was replaced with
ldf.get_signals()
the behavior was changed, instead of returning
None
the new methods will raise aLookupError
in the future there may be warnings enabled and possibly removed in later releases
Parsing
ldf.parseLDF(x)
withldf.parse_ldf(x)
, signatures are slightly different but functionally identicalldf.parseLDFtoDict(x)
withldf.parse_ldf_to_dict(x)
This discussion was created from the release v0.10.0.
Beta Was this translation helpful? Give feedback.
All reactions