GLA Summit 2025/Implementing a "SOLID" File Read/Write API: Difference between revisions
Created page with "{{infobox |category=presentation |icon=GLASummitButton.png |presentation-conference=GLA Summit 2025 |presentation-presenter=Vijayanth Reddy Kandukuri }} {{presentation |presenters=Vijayanth Reddy Kandukuri |abstract=Building on my previous presentation idea, "A Fluid Understanding of the SOLID Design Principles and their use in LabVIEW", I would like to illustrate implementing the SOLID Design Principles in a real project. The LabVIEW File Read/Write VIs have two issue..." |
(No difference)
|
Latest revision as of 10:59, 28 November 2025
 | |
|---|---|
| Conference | GLA Summit 2025 |
| Presenters | Vijayanth Reddy Kandukuri |
Building on my previous presentation idea, "A Fluid Understanding of the SOLID Design Principles and their use in LabVIEW", I would like to illustrate implementing the SOLID Design Principles in a real project.
The LabVIEW File Read/Write VIs have two issues. The first, LabVIEW happily allows the developer to write code that reads from a write-only file or writes to a read-only file at edit time. It is only when the program is run that an error pops up. It would be better if the error is at compile time rather than at run time. The second issue is a long standing bug that gives erroneous outputs with Preallocated Read from Binary File. Both of these issues can be circumvented with an OOP based approach.
LabVIEW on Windows also offers support for DLL based or .NET file read/write. If interfaces are added into the above API, we could provide the end user with a really flexible API that allows them to choose which type of flie read/write they wish to do as well.
I would like to illustrate all this with code I am developing at present. I feel it would help cement the understanding of the more theoretical aspects of my other presentation.