Forums Register Login

UB: Instantiation of Data class, automatic tests

+Pie Number of slices to send: Send
Hi!
I'm just wrapping up my project and started to think (seemed like a good time to start thinking ;-).
In my solution there should only be one Data class which all threads should access and it is instantiated with the path to the db-file. If there are multiple instances of the data class which have the same path to the database there is a risk that data may be coruppted.
I have stated this in the documentation but do you think that the code should be changed to take care of this situation. I cant really decide how to do, it doesnt require too much code to fix this but still the code becomes more complex. Also, it feels a bit strange to write code that is not needed in my solution.

What worries me is that in my database code I am in control of how the data class is instantiated but when Sun runs the automatic tests they may have a different approach to how things are instantiated.

Best Regards,
Kalle
I promise I will be the best, most loyal friend ever! All for this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 528 times.
Similar Threads
stuck by lock
finalization
How friendly are they when running my submission?
automatic failure
Take this Testing Tool for Data Class
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 10:47:51.