Daniel Einspanjer wrote:
> "Bram Moolenaar" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > Daniel Einspanjer wrote:
> >> ( ( ( long )( yr - 1900 ) >= _BASE_YEAR ) && ( ( long )( yr - 1900 ) <=
> >> _MAX_YEAR64 ) )
> >
> > Where is that assertion? I don't see it in the source code. Isn't this
> > a problem in one of the libraries?
> >
> > I dated a file Jan 1 1969 and Vim could edit it just fine. This is on
> > FreeBSD.
> >
> > What OS? How was Vim compiled?
>
> I'm sorry I didn't give enough details. Maybe this is just a red herring
> due to the fact that I'm compiling it myself. It seems to be that
> __loctotime64_t just can't handle any time before 197001010000.00 localtime.
> ::shrug::
>
> That assert is actually in c:\Program Files\Microsoft Visual Studio
> 8\VC\crt\src\dtoxtm64.c. Brief call stack is:
> > vimd.exe!__loctotime64_t(int yr=1969, int mo=12, int dy=31, int hr=20, int
> > mn=0, int sc=0, int dstflag=-1) Line 67 + 0x57 bytes C
> vimd.exe!_stat64i32(const char * name=0x0012fcb0, _stat64i32 *
> buf=0x0012fdd0) Line 195 + 0x37 bytes C
> vimd.exe!stat(const char * _Filename=0x0012fcb0, stat * _Stat=0x0012fdd0)
> Line 61 + 0xd bytes C
> vimd.exe!vim_stat(const char * name=0x00a7ff30, stat * stp=0x0012fdd0)
> Line 523 + 0x10 bytes C
Thus the problem happens inside a library call? I don't think I can fix
that in Vim. Perhaps you can install FreeBSD? :-)
--
hundred-and-one symptoms of being an internet addict:
85. Choice between paying Compuserve bill and paying for kids education
is a no brainer -- although a bit painful for your kids.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
