Efraim Flashner <efr...@flashner.co.il> skribis:
> On Fri, 12 Feb 2016 19:44:46 -0500
> Leo Famulari <l...@famulari.name> wrote:
>
>> On Sat, Feb 06, 2016 at 12:45:39PM -0800, Steve Sprang wrote:
>> > It looks like downloading the tarball from erlang.org works now.
>> > Here's an improved patch.
>> > + (lambda* _
>> > + (let ((escripts
>> > + (append
>> > + (find-files "." "\\.escript")
>> > + (find-files "lib/stdlib/test/escript_SUITE_data/")
>> > + '("erts/lib_src/utils/make_atomics_api"
>> > + "erts/preloaded/src/add_abstract_code"
>> > + "lib/diameter/bin/diameterc"
>> > + "lib/reltool/examples/display_args"
>> > + "lib/reltool/examples/mnesia_core_dump_viewer"
>> > + "lib/snmp/src/compile/snmpc.src"
>> > + "make/verify_runtime_dependencies"
>> > + "make/emd2exml.in"))))
>> > + (substitute* escripts
>> > + (("/usr/bin/env") (which "env"))))))
>> > + (add-before
>> > + 'configure 'set-erl-top
>> > + (lambda* _
>> > + (setenv "ERL_TOP" (getcwd)))))
>>
>> I _think_ that 'lambda _' would be appropriate here. I need a real
>> Schemer to weigh in ;)
>>
>
> I'm definately not a "real schemer," but since the lambda only leads into the
> let (ie. one item), I'm pretty sure 'lambda _' should be sufficient.
Correct. ‘lambda*’ is for when one wants to use optional or keyword
arguments (info "(guile) lambda* and define*").
Ludo’.
