Why use C.realpath instead of path/filepath.EvalSymlinks in plugin/plugin_dlopen.go?

vimalk78 · April 13, 2017, 12:48pm

i am just curious to know that why in plugin/plugin_dlopen.go it uses C.realpath instead of EvalSymLinks from path/filepath package

github.com

golang/go/blob/master/src/plugin/plugin_dlopen.go#L43-L52


func lastIndexByte(s string, c byte) int {
	for i := len(s) - 1; i >= 0; i-- {
		if s[i] == c {
			return i
		}
	}
	return -1
}


func open(name string) (*Plugin, error) {

calmh · April 13, 2017, 12:58pm

Usually these sort of “odd” decisions in the standard library are about managing dependencies. The path/filepath package is large and depends in turn on things like Unicode tables. The plugin package is small and there is value in not unnecessarily pulling in extra packages for all users of it. It already has the C dependency.

system · July 12, 2017, 12:58pm

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.