0000949: Make fileutil usable in projects (move fileutil.h to include dir)

(0001211)
andras (administrator)
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!

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4099.html [^]

(0001212)
till (reporter)
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 ;)

(0001213)
rhornig (administrator)
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.

(0001214)
till (reporter)
2016-04-13 07:48

I agree. I will copy the code

(0001286)
andras (administrator)
2017-02-01 14:42

Closing, according to the discussion.

(0001287)
andras (administrator)
2017-02-01 14:43

Closing, according to the discussion.

Notes
(0001211) andras (administrator) 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! http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4099.html [^]

(0001212) till (reporter) 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 ;)

(0001213) rhornig (administrator) 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.

(0001214) till (reporter) 2016-04-13 07:48	I agree. I will copy the code

(0001286) andras (administrator) 2017-02-01 14:42	Closing, according to the discussion.

(0001287) andras (administrator) 2017-02-01 14:43	Closing, according to the discussion.

Issue History
Date Modified	Username	Field	Change
2016-02-22 15:45	till	New Issue
2016-04-12 18:32	andras	Note Added: 0001211
2016-04-12 20:38	till	Note Added: 0001212
2016-04-12 21:26	rhornig	Note Added: 0001213
2016-04-13 07:48	till	Note Added: 0001214
2017-02-01 14:42	andras	Note Added: 0001286
2017-02-01 14:42	andras	Status	new => resolved
2017-02-01 14:42	andras	Resolution	open => won't fix
2017-02-01 14:42	andras	Assigned To	=> andras
2017-02-01 14:43	andras	Note Added: 0001287

Relationships