OMNeT++/OMNEST Bug Tracker - OMNeT++
View Issue Details
0000949OMNeT++simulation kernelpublic2016-02-22 15:452017-02-01 14:43
resolvedwon't fix 
0000949: Make fileutil usable in projects (move fileutil.h to include dir)
We are working on custom result managers. Filesystem manipulations are tasks to do there regularly (create directories, remove files, ...)
Would be very helpful to have fileutil.h in the includes to make it usable in such code.
No tags attached.
Issue History
2016-02-22 15:45tillNew Issue
2016-04-12 18:32andrasNote Added: 0001211
2016-04-12 20:38tillNote Added: 0001212
2016-04-12 21:26rhornigNote Added: 0001213
2016-04-13 07:48tillNote Added: 0001214
2017-02-01 14:42andrasNote Added: 0001286
2017-02-01 14:42andrasStatusnew => resolved
2017-02-01 14:42andrasResolutionopen => won't fix
2017-02-01 14:42andrasAssigned To => andras
2017-02-01 14:43andrasNote Added: 0001287

2016-04-12 18:32   
Well, the common/fileutils stuff is not really well designed or comprehensive, just barely enough to do the file manipulation needed inside OMNeT++. I'll be very happy to give it up, once a good replacement comes along. For example this, a standard C++ filesystem API (link below). I'm really looking forward to it coming! [^]
2016-04-12 20:38   
I agree that the lack of an api (apart from boost) is disturbing. But until there is something better it would really help to have the opp implementation available, otherwise I would have to come up with an even worse design ;)
2016-04-12 21:26   
The problem is. Once something is an API, you have to maintain it, keep it stable and not break it. It would be even acceptable if you copy/paste the specific routines into your own project. This way, you would have the functionality, but it would be local to your project.
2016-04-13 07:48   
I agree. I will copy the code
2017-02-01 14:42   
Closing, according to the discussion.
2017-02-01 14:43   
Closing, according to the discussion.