[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lay groundwork for exec. ext. support
From: |
Akim Demaille |
Subject: |
Re: Lay groundwork for exec. ext. support |
Date: |
18 Jun 2001 19:17:19 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Academic Rigor) |
| On Mon, Jun 18, 2001 at 06:34:05PM +0200, Tim Van Holder wrote:
| : I'd like to see this included in 2.51 as groundwork for
| : a working solution in 2.52. It should not affect any
| : existing scripts (I think).
|
| Using something like
|
| ac_executable_forms='${base} ${base}.exe ${base}.com'
|
| base=perl eval ac_candidates=\"$ac_executable_forms\"
| for ac_candidate in $ac_candidates; do
| ...
| done
|
| is more flexible than
|
| for ac_exec_ext in '' $ac_executable_extensions; do
| ...
| done
|
| I can't think of a platform where it is necessary right now though,
| but more flexibility never hurts and it avoids the '' special case
| you use.
I'm not found of eval :(
Why not including '' in the list? And define
: ${ac_executable_forms="''"}
in the DEFAULT section?