To whoever downvoted me, perhaps you're right. At the very least I should have tried to say why.

OK, let's try and interpret the parent post in a way that makes sense to me.

If your config data is effectively embedded in code and well isolated from the rest so that it could be extracted into an ini file easily, I'd buy that. I guess you lose flexibility as you have to recompile, but ok. Perhaps it's safer too.

> and [the code is] already using the best format you have for expressing your business domain logic

Well, often a good format for an abstract statement of actions is a list or grid of data which drives the code's decisions and actions. In that sense, if you've respected that, that's part of your config file (whether external, as a file, or embedded in the code though hopefully well isolated).

If none of this is your intention, could you let me know what you're thinking, with concrete examples please?