File Structure vs Data Structure

[aronclark1017]

TL;DR

have been debating for some time now about weither to access data from file or use list across entire application. In some cases it is more convenient to access data from file where only single instance is used. Such as for example creating new object in main form then listing all objects in next form. My first intuition would be to create a new file in the main form then read all the files into a list within the next form. My question if it would be better practice to simply just read the ...

 

[aronclark1017]

Maybe just save the object. Is the structure all because is crook to hide from.

 

[DaveC426913]

There are as many ways to code a procedure as there are coders. The question is what are your priorities?

I can't speak for your circumstance but, generally reading and writing files are some of the slowest operations a system and language can perform. The more file-writing your system does, the slower it will be, and the less scalable it will be.

Even if those are not priorities for this particular application, speed and scalability are still excellent criteria on which to build your coding philosophy.

 

[aronclark1017]

Imagine the diagram as a button form. In .net can tag value to button.

 

[DaveC426913]

Er, what?

I mean, I know how .net works, but what does that have to do with your opening post?

 

[aronclark1017]

Is a good post trust is. To debate about wether to use data structure or just simply file directory. Similar to a grid, the file directory is a data structure in its self one that often time I use without reading into a data structure especially when working with .net forms. However I suspect such could be criticism with argument such as the files could be possibly modified outside the application.

 

[berkeman]

Is a good post trust is.

 

[aronclark1017]

Toyoda...not to mention a data structure using node for file list and directory is slow as hell