Convenience Features

Some parts of my library have “convenient” functions. For example, a container class may have a function to parse information from a string. These functions are not necessarily necessary (or needed) all the time, so I would like to put them in separate files so that they can be included or left according to the needs of users.

How should this be structured? Should I put all the “convenient” things in the header files in a separate folder? Or maybe it belongs to a completely separate library ...?

How do such large libraries (like Boost) make? Or do they just avoid it at all?

+3
source share
2 answers

"" - , , , , , , .

, ? , ?

- () "parseString" - , ?

+1

, ( C/++, , Ruby - , c.). , , .

0

All Articles