| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Felipe Contreras wrote: |
| 5 |
| On Sat, Feb 23, 2008 at 10:45 PM, Alec Warner <antarus@g.o> wrote: |
| 6 |
|> On 2/20/08, Felipe Contreras <felipe.contreras@×××××.com> wrote: |
| 7 |
|> > b) Error are difficult to handle since bash doesn't have exceptions |
| 8 |
|> |
| 9 |
|> I disagree here: most errors are fatal anyway any non fatal errors can |
| 10 |
|> be printed and saved via the elog facility. |
| 11 |
| |
| 12 |
| Yes, for the most common usage that's true, but that think about this |
| 13 |
| example: I'm compiling gstreamer-plugins-good, which needs libraw1394, |
| 14 |
| but the compilation fails, perhaps that user is not interested in that |
| 15 |
| particular plugin so a dialog can pop up and the user can choose if to |
| 16 |
| continue without the libraw stuff or fail. |
| 17 |
| |
| 18 |
| I'm sure that can be done without exceptions but as the complexity |
| 19 |
| increases properly checking/passing around error values/messages |
| 20 |
| becomes tedious. |
| 21 |
| |
| 22 |
|
| 23 |
That's what USE flags are for. |
| 24 |
|
| 25 |
- -- |
| 26 |
|
| 27 |
Luis F. Araujo "araujo at gentoo.org" |
| 28 |
Gentoo Linux |
| 29 |
|
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 32 |
|
| 33 |
iD8DBQFHwbyIBCmRZan6aegRArK/AJ9wBvqPZ9PErpxiVHgpkSLuCZIixQCdGiEB |
| 34 |
wvdMli4taTHJFVBoHYIzyLs= |
| 35 |
=/1k7 |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-dev@l.g.o mailing list |
Archives