1 |
On Tue, Jun 10, 2008 at 7:30 PM, Ciaran McCreesh |
2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
3 |
[...] |
4 |
> - it doubles the number of file reads necessary during resolution. |
5 |
|
6 |
The first read will cause the file to be cached for subsequent reads |
7 |
anyway, so the performance hit boils down to an additional read() call |
8 |
(which will probably be buffered by your file I/O library anyway, so |
9 |
it's unlikely to even result in a context switch). And even without, |
10 |
it is well worth the lack of fugliness in the ebuild name. |
11 |
|
12 |
> - it heavily restricts future syntax and meaning of EAPIs |
13 |
|
14 |
Not by much. It's just a header. |
15 |
|
16 |
> - it makes comments have meaning |
17 |
|
18 |
Just as much as #!/bin/bash and # vim: ... do |
19 |
|
20 |
Regards, |
21 |
-- |
22 |
Arun Raghavan |
23 |
(http://nemesis.accosted.net) |
24 |
v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056 |
25 |
e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com |
26 |
-- |
27 |
gentoo-dev@l.g.o mailing list |