TIs the text format fixes? If not, you could use json to make reading and writing easer with existing json libraries. The json syntax is very similar to what you have.
LI thought about json, but wasn't sure if it would support this specific syntax. For whatever reason, I cannot deviate from that syntax.
LWell, I did write something that does parse the files perfectly
LBut it's not json, hoooo no. I don't think it's very efficient to begin with but i can certainly share
Lmessage.txt4.01KB
L(ignore the comments on it, I got very hyperfixated on state buildings for a bit and forgot to remove the comments complaining about something i already fixed.)
TAlthough this works, it will only work with this model. For a more dynamic implementation, you should use reflection. Newtonsoft.Json has attributes for defining custom keys for properties and for ignoring properties so you could do something similar.
TReflection is slower than directly referencing properties but generally only becomes a concern at a massive scale
LGot any links?
TReflection provides objects that describe assemblies, modules, and types in C#. If your code includes attributes, reflection enables you to access them.
TThere's an extension method for getting a custom attribute based on the attribute as generic
TGetCustomAttribute<>()
LHm. The scale I am working at goes up to about 4000 files for provinces alone, other types go about 300 or so
LI doubt that’s anything too rough on reflection but just for the sake of knowledge, would it be?
TThat would need benchmarking and depends on your setup.
TFor reference, I made an app that regularly reads about 600 lines of json with pretty deep nesting and on a Ryzen 7 2700x the operation is basically instantaneous
TSo reflection isn't "slow", it's just that direct references are blazing fast in comparison
LSounds pretty good then. I was moreover hoping to simplify my code in general to something both faster and a bit shorter on lines
TIf the use is niche then that works too
TThe more abstract approach is more useful for established formats used by multiple projects
LI’d say yeah it’s pretty niche. It only works on that specific file structure because that file structure is the bare necessity for another program
LFrankly if a project I’m working in is using an established format, I would probably better off implementing a Json reader
LI also wanted to delete this thread since I’ve long since sorted out the file handling
LMoving on to greater things like rebinding that data to my UI interfaces.
MUse the
/closePerfect thank you
A
This post has been marked as answered!