[splint-discuss] .splintrc and dir names with spaces
Ralf.Wildenhues at gmx.de
Tue Aug 24 11:42:40 EDT 2004
* Mike Solem wrote on Tue, Aug 24, 2004 at 05:28:34PM CEST:
> I see what you're doing, but can't get it to work for what I want.
> I'm assuming ~1 is some kind of name completion symbol. It seems
> to only work when there are 6 preceding characters. Example:
> -IC:/Docume~1/mydir # Works
> -IC:/Docum~1/mydir # Doesn't work
> -IC:/Documen~1/mydir # Doesn't work
> Looks like you also had 6 chars in your file (Progra~1). Is there any
> way around this limitation?
This has nothing to do with splint whatsoever. It is a legacy feature
of windows, providing backward compatibility of some sort to pre-VFAT
(DOS) style of 8.3 filenames (through a non-unique, history-dependent
mapping of long file names to short ones). Use as kludge to get around
the fact that splint does not really allow to provide spaces in options
within the splintrc file.
Still, somebody please fix this within splint, as it would IMHO hurt
very little on backwards compatibility (anybody having directories with
a " in their name should be considered insane anyway), and is the more
useful for macro definitions (-Dfoo="bar baz"). These, btw, need to
be fixed on the command line as well (why?).
More information about the splint-discuss