| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | dates |
PM>> Anyway, I rewrote dtsplit last night so that it can handle dates that PM>> aren't quite up to scratch. I haven't done extensive tests but it PM>> appears to be working. Basically, this version isn't particularly fussy PM>> about spaces and leading zeros. It will even handle a date such as PM>> "1JAN94 1:2:3" correctly. PE> I don't know whether to flog that or not. I think I'll keep the one I've PE> got, because at the moment, it will continue processing, no matter what PE> the date is, but it will flag every violation as such. BFN. I'm now using it in my packet sorter, so (eventually) you'll get it and you can do what you like with it. It was written to maximise the chance of handling the date and time, even if it has to do a little fiddling on the way through. For instance, if you pass it an invalid time, say "25:66:77" it'll merrily change this to "23:59:59" without ever informing you there's a problem. While I was testing the program and comparing the results to the original dtsplit, I noticed one discrepency. If you use a date of "01 Jan 05", the original will treat the year as 1905 while mine will treat it as 2005. Paul --- GoldED/2 2.42.G1114* Origin: It's not even a nice place to visit (3:711/934.1) SEEN-BY: 640/305 711/934 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.