On 07.04.2014 14:42, Gerhard Sittig wrote: > So there are valid reasons to not process those filesystem > entries. Would it be useful to not emit the warnings then?
The warnings wouldn't even appear if cscope were allowed to do the tree traversal by itself. I.e. cscope -R already skips symlinks silently, without emitting any warnings (see issrcfile() testing for S_ISREG()). You only get those warnings if cscope was explicitly told, by way of a name list file (cscope.index, or -i option), to index a given set of files, and there are symlinks in that list. All you would have to do is keep the symlinks out of that name list file. I don't see a need for a change in cscope here. The desired behaviour can be had without changing cscope. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Cscope-devel mailing list Cscope-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cscope-devel
