-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steve Long wrote:
[...]
>>> for ((i=0;i<100000;i++)); do echo /usr/share/doc/${P}/examples >
>>> /dev/null;
>>> real 11.25
>>> real 9.24
>> So that's what, on the order of 20 microseconds faster for each iteration?
>>
> Or ~18%. (You shouldn't use the first iteration in general, btw.)
I've not really got an opinion on the topic, per se, but fwiw, this is
really not a meaningful statistic. *If* parsing strings in the ebuild is
not a trivial part of the overall ebuild parsing process, then yes, this
is a significant gain and should be treated as such. I find it unlikely
that this would be the case.
I'm not sure how one can go about measuring the impact of this on ebuild
parsing as a whole. Maybe make take a few "typical" ebuilds, change
quoting style, and run it through ebuild.sh in a loop. All the inherited
eclasses would need to change too, though, I guess.
Regards,
Arun
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkj2sxgACgkQ+Vqt1inD4uzW3wCfancNcJxcyHerjSZdZfK9UKb7
k5oAn0186/lLTAS2+n1Z7egzhAP1kISV
=CkaZ
-----END PGP SIGNATURE-----
