micky@cunixc.cc.columbia.edu (Micky Liu) (03/20/89)
I have the Programmer's Toolkit for PC-NFS V3.0 and was wondering about the status of this software product... Is this product being upgraded at all? I am running Microsoft C V5.1 and am not too happy with consistency problems... - Some objects are defined more than once between toolkit supplied header files and msc supplied header files. - Some objects are not defined to be of the same type between the header files. Although the examples that I've found had types of the same size, I suspect that there are some problems with usage. - Some of the libraries have objects that were compiled in uppercase, making it necessary to link the objects by hand since the default for the compiler is to use /NOI (no ignore case). - Yet, some of the libraries are all lowercase... - Since the new version of the MS C compiler uses 'combined' libraries, the default library search the was compiled into the toolkit objects causes many unnecessary prompts for libraries that don't exist. Solution is to use /NOD (no default library search), but then you must specify the standard library, [smcl]libce.lib (like /lib/libc.a). Big question is, will there be another version of the toolkit updated to conform to the new compilers? Thanx, Micky Liu arpa: micky@cunixc.cc.columbia.edu uucp: ...!rutgers!columbia!cunixc!micky bitnet: malua@cuvmc
steve@raspail.cdcnet.cdc.com (Steve Schonberger) (03/23/89)
In article <1319@cunixc.cc.columbia.edu>, micky@cunixc.cc.columbia.edu (Micky Liu) writes: > I have the Programmer's Toolkit for PC-NFS V3.0 and was wondering > about the status of this software product... Is this product being > upgraded at all? I am running Microsoft C V5.1 and am not too happy > with consistency problems... > Big question is, will there be another version of the toolkit updated to > conform to the new compilers? Have you run it successfully with older versions of the Microsoft compiler, or with the Borland compiler? If it works with them and doesn't work with the new Microsoft compiler version, I'd phrase the question: Will there be another version of the compiler libraries that remains consistent with previous behavior? If it didn't work before, I'd blame the problem on the NFS libraries, but if it works with other compilers, I'd blame it on 5.1. I don't know either way whose fault the problem is. Steve Schonberger steve@raspail.cdcnet.cdc.com