Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!mcvax!ukc!stl!stc!datlog!djh From: djh@datlog.co.uk ( Dave Howorth ) Newsgroups: comp.std.c Subject: Significant name length list Summary: Lets build one! Message-ID: <2146@dlvax2.datlog.co.uk> Date: 19 Jul 89 10:46:59 GMT References: <2619@yunexus.UUCP> <547@cybaswan.UUCP> <1989Jul14.162834.2721@utzoo.uucp> <33148@apple.Apple.COM> Reply-To: djh@datlog.co.uk ( Dave Howorth ) Organization: Data Logic Ltd, Queens House, Greenhill Way, Harrow, London. Lines: 30 In article <33148@apple.Apple.COM> Jonathan Patrick Leech writes: > How about if someone identifies the offending environments. >Presumably linkers introduced in the future will not suffer under the >6-character restriction, so people willing to flush the currently >offending systems from their porting base could work with a more >flexible limit. > Jon Leech (leech@apple.com) > Apple Integrated Systems I think this is an excellent idea, so lets do it! We can be positive by building a list open to all compilers which gives the implementation limits they impose. We should collect: - compiler/linker/platform name and version - operating system (UN*X, M*-DOS, other) - ANSI (yes/no) - internal name significant length - external name significant length - external name case significant (yes/no) - date for 31 character case significant external name version I am looking for this information for some work I am doing, and am prepared to collate and summarise to save net bandwidth. I would particularly welcome statements direct from compiler and hardware vendors! So mail me with what you know! Dave Howorth : djh@datlog.co.uk : +44 1 863 0383 Data Logic, Queens House, Greenhill Way, Harrow HA1 1YR, ENGLAND