On Tue, Mar 6, 2012 at 8:03 AM, Kenneth Lundin <> wrote:
> What I meant was that I am not convinced that it is necessary and very
> useful to have the include files
> inside an archive (while using them).
>> But it might be possible to convince me :)
Yaws and gettext requires some .hrl files for compiling dynamic pages.
I think there may be other cases where code is compiled during runtime
where it is useful to have access to the .hrl files.
/Anders
>> /Kenneth
>>> On Tue, Mar 6, 2012 at 1:20 PM, Ulf Wiger <> wrote:
>>>>>> On 6 Mar 2012, at 13:02, Kenneth Lundin wrote:
>>>> There is no timeline and it is even questionable if it should ever work.
>> What is the argument
>> for having the include files inside the archive?
>>>>>> I ran into this problem, and made an "OTP patch" for it:
>>>>http://article.gmane.org/gmane.comp.lang.erlang.general/52060>>>> (Don't think I ever submitted it as a patch, since Håkan and I disagreed
>> on some of the implementation details).
>>>> I wrote: "The idea (see http://github.com/esl/run_eqc) was that it should
>> be possible to deliver an application as a single archive, supporting
>> command-line operations, interactive code loading, and compilation including
>> hrl files, parse_transforms etc., without having to unpack the archive."
>>>> Philip Stanhope wrote: "Very cool. I can see how this will make
>> deployments very easy."
>>>>http://article.gmane.org/gmane.comp.lang.erlang.general/52061>>>> Dizzy writes: "+1 on this feature -- it opens some very interesting
>> doors."
>>>>>>> _______________________________________________
> erlang-questions mailing list
>>http://erlang.org/mailman/listinfo/erlang-questions>