[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: support .f03 and .F03
From: |
Ralf Wildenhues |
Subject: |
Re: FYI: support .f03 and .F03 |
Date: |
Mon, 26 Feb 2007 05:43:05 +0100 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
* Gary V. Vaughan wrote on Mon, Feb 26, 2007 at 05:24:18AM CET:
> On 25 Feb 2007, at 20:05, Ralf Wildenhues wrote:
>
> Once I've caught up with my gnu mailing list backlog, I'll have about
> 10 hours a week or so to help out with libtool-2.0 (and then m4-2.0)
> for a few months :-)
Great.
> Dusting off my sed-fu, and with wider quoting for Eric ;-)
>
> func_version ()
> {[
> $SED -n '
> :a
> /[1-9][0-9]*[,-]$/N; s/[1-9][0-9]*[,-]\n# *//; ta
Exactly one space between "t" and "a".
> /^# '$PROGRAM' (GNU /,/# warranty; / {
> s/^# //
> s/^ *$//
> /\((C)\)[ 0-9,-]*\( [1-9][0-9]*\)/\1\2/
"s" missing at beginning of line.
> p
> }' < "$progpath"
> exit $?
> ]}
Then it looks almost good, except that I think we should be tolerant to
people who put trailing spaces in their files. I guess if you change
the second line to
/[1-9][0-9]*[,-][ ]*$/N; s/[1-9][0-9]*[,-][ ]*\n# *//; t a
that should be ok. A bummer that this won't work with UNICOS sed any
more. I successfully ran CVS Libtool on the cray-cyber museum system a
couple of years ago. Sigh.
> >FWIW, we could also just write 2003-2007 in the copyright
> >statement, no?
> If you do want to do that, best check with RMS first...
Yeah, never mind, I think I knew the answer already...
Cheers,
Ralf