Re: date/time functions

2000-06-01 Thread Dan Harkless
Shantonu Sen <[EMAIL PROTECTED]> writes: > If noone has *severe* objections, I'd like to drop AT&T lex support in > favor of a more straightforward and maintainable flex version. By all means. > A pre-flexed version will come with the distribution, and like Dan said, > it's fairly straightforw

Re: date/time functions

2000-05-31 Thread Shantonu Sen
> I updated my sources and re-ran against Solaris and AIX using lex and > it doesn't appear to work. The file gets lexed without a hitch now, > but the .c file it outputs isn't usable. Well, in any event, taking out the case-insensitivity sped up the processing by 1.7% (that's not very scientifi

Re: date/time functions

2000-05-31 Thread Dan Harkless
Doug Morris <[EMAIL PROTECTED]> writes: [...] > dtimep.c:263: warning: label `yyfussy' defined but not used [...] Heh heh -- that one's pretty ironic. All those errors are why I was thinking it'd be reasonable to only use flex (if available), not lex. As for the warnings, once we get the dtime

Re: date/time functions

2000-05-31 Thread Doug Morris
Shantonu Sen wrote: >Did you check these in? They didn't appear to be in the CVS version. No, I thought it best to just mail you the patch since you were probablly working on the code anyway to avoid conflicts (and also since I hadn't tested it against AIX yet). I updated my sources and re-ran

Re: date/time functions

2000-05-31 Thread Shantonu Sen
> I set the memory options back, removed %option noyywrap, and added > #undef yypwrap to the header section. This appears to work in Solaris > and in flex on my linux system. Here's the patch... Did you check these in? They didn't appear to be in the CVS version. Anyway, I added back the memory l

Re: date/time functions

2000-05-30 Thread Doug Morris
Shantonu Sen wrote: >> on AIX 4.3.3 lex fails with >yikes! it's not that big a program! hmm, in the old lexer, there were >some options at the beginning like so: >%e 2000 >%p 5000 >%n 1000 >%a 4000 > >I didn't spend too much time looking into them. Could they be memory >usage hints? That's them e

Re: date/time functions

2000-05-30 Thread Dan Harkless
Shantonu Sen <[EMAIL PROTECTED]> writes: > Did either AIX or solaris have a problem with the lexed version > dtimep.c which is in CVS? hopefully that's ANSI C. It worked fine on AIX (4.1). IIRC, Solaris succeeds in lex'ing the file, so I've never tried the pre-canned one on it. > > Actually, i

Re: date/time functions

2000-05-30 Thread Shantonu Sen
> on AIX 4.3.3 lex fails with > > $ make dtimep.c > lex -nit dtimep.lex > dtimep.c > Error: 1285-328 There is not enough memory for final processing. > make: *** [dtimep.c] Error 1 > > lex has a few options for playing with the memory. I'll see if I can > get a patch to you that doesn't break th

Re: date/time functions

2000-05-30 Thread Doug Morris
Shantonu Sen wrote: >I've written a new date lexer, which you can find in sbr/dtimep.lex. It: >1) works >2) works with flex (I admittedly have not tried it with lex, although it > works in flex's lex compatibility mode, if that means anything). I did a bit of testing on the systems at work: on

date/time functions

2000-05-29 Thread Shantonu Sen
I've written a new date lexer, which you can find in sbr/dtimep.lex. It: 1) works 2) works with flex (I admittedly have not tried it with lex, although it works in flex's lex compatibility mode, if that means anything). 3) works without any "sed hackery", as was mentioned a few weeks ago. Thi