Re: C programmers (particularly those who use LCC32).
From: Srin Tuar (SrinTuar_at_example.net)
Date: 06/24/04
- Next message: rose: "Re: タソ"
- Previous message: jim_breen_at_idontreadhotmail.com: "Re: C programmers (particularly those who use LCC32)."
- In reply to: Paul Blay: "Re: C programmers (particularly those who use LCC32)."
- Next in thread: JamesM: "Re: C programmers (particularly those who use LCC32)."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Jun 2004 03:35:48 GMT
> Pretty easy for a few screens of code. A giant pain in the for 63
> .c files & alsorted extras.
ergo, the command line:
for file in *.c ; do convert_file_to_sjis $file; done
for file in *.c ; do highbytes2constants.pl $file; done
convert_file_to_sjis()
{
iconv -f whatever -t sjis < $1 > $1.converted
mv $1 $1.bak
mv $1.converted $1
}
etc...
> Apart from anything else lcc has a 500
> char limit / line. Editing 27 lines to get it to compile wasn't a problem,
> I hate to think how many lines I'd have to edit if I went that route.
If your C code is anywhere near that limit it has problems, even bloating
the constants out. You must have some really strange code.
Even then, its not too hard to insert some newlines with a script.
- Next message: rose: "Re: タソ"
- Previous message: jim_breen_at_idontreadhotmail.com: "Re: C programmers (particularly those who use LCC32)."
- In reply to: Paul Blay: "Re: C programmers (particularly those who use LCC32)."
- Next in thread: JamesM: "Re: C programmers (particularly those who use LCC32)."
- Messages sorted by: [ date ] [ thread ]