Re: Best way to communicate changing the output of a module

2013-12-26 Thread Yanick Champoux
On 13-12-26 11:16 AM, David Mertens wrote: This would be dependency hell. I think a prominent warning (as suggested by Aristotle) would be much better. Probably a better first approach, all in all. Assuming that this is not just over-engineering, considering how semantic versioning is still a

Re: Best way to communicate changing the output of a module

2013-12-26 Thread David Mertens
`/anick - This would be dependency hell. I think a prominent warning (as suggested by Aristotle) would be much better. Whether we should have this sort of environment variable around is a good question. How would we develop an awareness and use of this variable? David On Sun, Dec 22, 2013 at 11

Re: Best way to communicate changing the output of a module

2013-12-26 Thread David Mertens
To expand on Leon's suggestion, you could also provide some simple constants for often-used date/time formats, making it even easier for your users to invoke standard formatting. David On Mon, Dec 23, 2013 at 9:45 AM, Leon Timmermans wrote: > On Mon, Dec 23, 2013 at 12:48 PM, Shmuel Fomberg >