Please use dates in logs for module fixes.
BlitzMax Forums/BlitzMax Programming/Please use dates in logs for module fixes.
| ||
| Hi, it would be really good if each new ModuleInfo about bug fixes/improvements that are added to top of each BlitzModule included a date. Then we can see if the tweak has been added since the last full release or sync mods or whatever, as currently the only way I can tell is to backup the old mods and then compare them with the new one - this is a tad laborious. That's all I'm asking, just a dd/mm/yy date like this from now on: ModuleInfo "History: 1.16 Release 31/05/06" This would be so great, plus I thought it was kind of normal to add dates to logs about changes...any chance? pretty please |
| ||
| Agreed. |
| ||
| Actually, it should be mm/dd/yy :O |
| ||
| Actually, it should be something more explicit like "31 May 2006" - then there'd be no confusion regardless of where you live. |
| ||
| I agree. Great suggestion. I've gone through the task of comparing files looking for when a change was introduced as well! But I prefer yyyy/mm/dd :o |
| ||
| arg! so illogical :-) OK dd mmm yyyy e.g. 01 jun 2006 or just state the date format at the top of the file. |
| ||
| yyyy/mm/dd should be the standard Reason - easier to sort: 2001/09/11 after 1996/06/13 before 2004/01/05 |
| ||
| Such a for format is easier to recognize... 02, Jun, 2006 However it's ok to use anything if recognizable. |
| ||
| Really, I don't care, just fix stuff! ;) |
| ||
| I do care though :-) Mark1nc: Yeah I stick a reverse date on the front of all my invoices and files that I want to keep in order by creation date (not date modified). |
| ||
| c'mon use Unix Time since EPOCH: The Unix epoch is the time 00:00:00 UTC on January 1, 1970 this is a single number: The Unix time number is zero at the Unix epoch, and increases by exactly 86 400 per day since the epoch. Thus 2004-09-16T00:00:00Z, 12 677 days after the epoch, is represented by the Unix time number 12 677 × 86 400 = 1 095 292 800. This can be extended backwards from the epoch too, using negative numbers; thus 1957-10-04T00:00:00Z, 4472 days before the epoch, is represented by the Unix time number -4472 × 86 400 = -386 380 800. |
| ||
| interesting as a date discussion is, I'm really looking for support or a word from BRL if they will consider it. |
| ||
| I'd like to bump this to see if I can get an official response. Please add dates to module logs, pretty please :-) |
| ||
| The most illogical standard of course is the american one with mm/dd/yy - its simply stupid and not in any logical order. dd/mm/yy or yy/mm/dd is fine by me |
| ||
| yyyy-mm-dd here, since it's an ISO format, should be recognized everywhere. (and because of what Mark said) Also, agree'd with the above, although I am not currently a BMax user, but it does appear to be a bit of a no-brainer when you think about it no? |
   |