[Ecls-list] Name of init function.

[Waldek Hebisch]

I wonder about method ECL uses to generate name of init function.
It seems that probability of getting clash while low, is high enough
to be a problem.  Namely, I just got build due to such name clash:


;;; Note: Creating tag: "_eclIQwoAUxR6I1_mttWj3" for "/home/hebisch/axp1/ax-build3/src/interp/g-boot.o"
;;; Note: Creating tag: "_eclIQwoAUxR6I1_mttWj3" for "/home/hebisch/axp1/ax-build3/src/interp/g-util.o"
;;; Note: Found tag: "_eclIQwoAUxR6I1_mttWj3"
;;; Note: Found tag: "_eclIQwoAUxR6I1_mttWj3"
/home/hebisch/axp1/ax-build3/src/interp/g-util.o: In function `_eclIQwoAUxR6I1_mttWj3':
/home/hebisch/axp1/ax-build3/src/interp/g-util.c:2426: multiple definition of `_eclIQwoAUxR6I1_mttWj3'


Looking at other build logs I see that ECL used the same prefix
_eclIQwoAUxR6I1_ for several other files.  I wonder why ECL is using
so short names (only 18 variable characters in the name).  Also, given
relative shortness of the name using strong hash which mixes well
all ingredients seem preferable compared to current method which
seem to separately encode components.

-- 
                              Waldek Hebisch
hebisch at math.uni.wroc.pl