Removal of certain functions from ftl files as per our requirements

[himarajmb]

We are considering removing certain functions from FTL file that we don't plan to use in our case.
Could you help us understand the potential side effects of this action?

[mikir]

Unfortunately, we cannot help if we don't know what you are planning to remove (and from which FTL file). FTL files contain templates for the generated files, so if you remove something, you will directly influence the generated code.

[himarajmb]

There are some functions related to PackagingContext:


For every Class , these functions are getting generated , which we are not going to use and we don't want to test the unused functions.
As result , this is affecting our test code coverage.
We are planning to remove this unused functions from being generated by deleting it from all the ftl files.
The Question are as below:
Dose this removal will affect any behavior for normal flow of other functions?
What does this Packaging Context is used for?

[himarajmb]

Addition to the above mentioned points, we are also not using something like DeltaContext as well.

[mikir]

The Packing Context is used for the packed arrays. It is generated in C++ only if keyword packed is used in the Zserio schema. If you remove Packing Context feature from FTL, you will completely break the functionality of the generated code (serialization and deserialization won't work anymore).

[himarajmb]

We are not using any of the flt functions in our case
For Structure.cpp.ft

initializeChildren()
operator==
ParsingInfo
Operator
initPackingContext

For Enumeration.cpp.ftl

enumReflectable
initPackingContext

For Union.cpp.ftl

Operator
Assign
initPackingContext

And similar with the Choice.cpp.flt file as well.
Could you help us understand the potential side effects of this action and if it can be removed without affecting the normal flow?

[mikir]

I think that if you remove almost anything from FTL, you will be always in risk that the generated code will be broken.

If you need to get rid of some methods, it will be probably better to implement some script which will postprocess the generated code and which will remove unnecessary methods automatically.