Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #8821

13 year old C source code

From buck <buck@private.mil>
Newsgroups comp.lang.c
Subject 13 year old C source code
Date 2011-07-28 19:04 +0000
Organization Say What?
Message-ID <j0sbru0am8@news4.newsguy.com> (permalink)

Show all headers | View raw


I haven't programmed in a VERY long time and I never was much good at 
it anyway.  From this you can accurately imply that I'm the wrong 
person to be doing this.  However:

I have been tasked to determine the feasibility of updating 13 year 
old (pre ANSI) ASM and C source code for the purpose of compiling a 
64-bit executable.

The source code was last modified in November of 1998 and was compiled 
using C88 v3.03 and ASM88 v1.5, which are copyright Mark DeSmet 1987 
and 1986 respectively.

Are there any utilities that examine old C code and suggest how to 
make it compliant with current compilers?  I tried splint v3.1.2, but 
it crashes on line 110 of 824 lines and does not tell me how to 
correct the errors and warnings it does find.

Are there any utilities that examine 8086 ASM code and explain what to 
change to make it compile for a 64-bit CPU?  I type 'debug' in a CMD 
prompt in Vista in order to see the register names, but (of course) 
Vista has no DEBUG...

One of the things I'm completely stuck on is the difference in char.  
In the existing source code and with C88,

'static char v[]={-20,-124,-180,-93,-88,-73,-27,-146,9,-38,-179 ...'

works, but the values obviously violate current char (and unsigned 
char) rules.  If char is changed to long, the values seem to be 
accepted, but the function is called with a char variable.

Any suggested resources other than utilities would be appreciated, 
too.  Google hasn't been much help, so the above includes a request 
for suggested search phrases.
--
buck

Back to comp.lang.c | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

13 year old C source code buck <buck@private.mil> - 2011-07-28 19:04 +0000
  Re: 13 year old C source code jacob navia <jacob@spamsink.net> - 2011-07-28 21:30 +0200
    Re: 13 year old C source code Francois Grieu <fgrieu@gmail.com> - 2011-07-28 21:35 +0200
      Re: 13 year old C source code jacob navia <jacob@spamsink.net> - 2011-07-28 21:48 +0200
        Re: 13 year old C source code Keith Thompson <kst-u@mib.org> - 2011-07-28 13:37 -0700
    Re: 13 year old C source code buck <buck@private.mil> - 2011-07-28 20:28 +0000
  Re: 13 year old C source code Francois Grieu <fgrieu@gmail.com> - 2011-07-28 21:31 +0200
  Re: 13 year old C source code Keith Thompson <kst-u@mib.org> - 2011-07-28 13:00 -0700
    Re: 13 year old C source code "Scott Fluhrer" <sfluhrer@ix.netcom.com> - 2011-07-28 18:10 -0400
      Re: 13 year old C source code Keith Thompson <kst-u@mib.org> - 2011-07-28 15:27 -0700
  Re: 13 year old C source code Rich Webb <bbew.ar@mapson.nozirev.ten> - 2011-07-28 15:53 -0400
  Re: 13 year old C source code Roberto Waltman <usenet@rwaltman.com> - 2011-07-28 16:18 -0400
    Re: 13 year old C source code Roberto Waltman <usenet@rwaltman.com> - 2011-07-28 16:34 -0400
  Re: 13 year old C source code Ben Pfaff <blp@cs.stanford.edu> - 2011-07-28 13:36 -0700
  Re: 13 year old C source code gordonb.mgm25@burditt.org (Gordon Burditt) - 2011-07-28 15:37 -0500
    Re: 13 year old C source code Robert Wessel <robertwessel2@yahoo.com> - 2011-07-28 17:33 -0500
      Re: 13 year old C source code gordonb.2omx0@burditt.org (Gordon Burditt) - 2011-07-28 18:48 -0500
        Re: 13 year old C source code Robert Wessel <robertwessel2@yahoo.com> - 2011-07-28 19:26 -0500
    Re: 13 year old C source code BGB <cr88192@hotmail.com> - 2011-07-28 16:09 -0700
  Re: 13 year old C source code Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-08-03 08:17 +0000

csiph-web