thanks for providing such a library, it's been a while since I've been looking at something similar.
Could you provide more information regarding the library's footprint and execution time for whatever processor you've tested this it on?
Also, do you have any plans to move away from the vector library? Vectors tend not to be supported that well by embedded systems...
Do you have any recommendation on how to minimize the footprint of this library to a minimum? For example, I am only interested in generating xml files on the fly (directly written to a file, no buffering in RAM).
Jean
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jean.
Thanks for your contribute on this forum, now I know someone is really interested on this project.
Well, actually the library doesn't have the possibility to compile only part of it, but it could be a good idea.
I agree someone could be interested only in the rapid file writer, so it should be a good idea to introduce a conditional build system in order to decide which features to enable.
So I'm planning to add these new features:
1) Selective build system
2) Use of namespaces to separate library names to others
3) The rewrite of the parser using FLEX+BISON (probably bison++ or something similar)
I think I could work sequantially on them, for example I could add the 1) and 2) very quickly (releasing for example a 0.1.1) and then work on the parser.
I have tested this library on x86, amd64 (to verify) and powerPC archs, working with Linux, MacOSX and VxWorks.
About the vector class, I could try to find an alternative to it, I know sometimes STL support is not used in embedded systems.
So please give me a feedback to this post.
Thank you so much
Marco
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
thanks for providing such a library, it's been a while since I've been looking at something similar.
Could you provide more information regarding the library's footprint and execution time for whatever processor you've tested this it on?
Also, do you have any plans to move away from the vector library? Vectors tend not to be supported that well by embedded systems...
Do you have any recommendation on how to minimize the footprint of this library to a minimum? For example, I am only interested in generating xml files on the fly (directly written to a file, no buffering in RAM).
Jean
Hi Jean.
Thanks for your contribute on this forum, now I know someone is really interested on this project.
Well, actually the library doesn't have the possibility to compile only part of it, but it could be a good idea.
I agree someone could be interested only in the rapid file writer, so it should be a good idea to introduce a conditional build system in order to decide which features to enable.
So I'm planning to add these new features:
1) Selective build system
2) Use of namespaces to separate library names to others
3) The rewrite of the parser using FLEX+BISON (probably bison++ or something similar)
I think I could work sequantially on them, for example I could add the 1) and 2) very quickly (releasing for example a 0.1.1) and then work on the parser.
I have tested this library on x86, amd64 (to verify) and powerPC archs, working with Linux, MacOSX and VxWorks.
About the vector class, I could try to find an alternative to it, I know sometimes STL support is not used in embedded systems.
So please give me a feedback to this post.
Thank you so much
Marco