On Sat, Dec 19, 2009 at 3:06 PM, dysinger <t...@dysinger.net> wrote:
> The main roadblock for me in interop with erl code is hrl files.  Some
> of the core erlang libs use them (
> http://www.erlang.org/doc/man/file.html#read_file_info-1
> ) and they are _AFAIK_ unavailable inside LFE.

> I know robert mentioned it was going to be hard to do that (last
> spring).  Any update? What can we do for erlang code that needs Erlang
> macros and records defined in an hrl file?

> --

> You received this message because you are subscribed to the Google Groups
> "Lisp Flavoured Erlang" group.
> To post to this group, send email to
> lisp-flavoured-erlang@googlegroups.com.
> To unsubscribe from this group, send email to
> lisp-flavoured-erlang+unsubscribe@googlegroups.com<lisp-flavoured-erlang%2B unsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/lisp-flavoured-erlang?hl=en.

> What I've been doing is rewriting the .hrl files as .lfe files (with
> defrecord), and using include-file at the top of the .lfe files.

> It is kind of a pain, but it ends up working out for the most part because
> (IMO) the macros generated by defrecord are quite a bit
> nicer to work with than the ones generated by the default Erlang records
> stuff.

> Are there other 'erlang' macros that would be difficult to replicate? or
> are we talking about record stuff mostly?

> Maybe we can startup a collection of rewritten .hrl files to make it a bit
> less painful?

> I'll happily donate the yaws_api.lfe that I have.

> On Sat, Dec 19, 2009 at 3:06 PM, dysinger <t...@dysinger.net> wrote:

>> The main roadblock for me in interop with erl code is hrl files.  Some
>> of the core erlang libs use them (
>> http://www.erlang.org/doc/man/file.html#read_file_info-1
>> ) and they are _AFAIK_ unavailable inside LFE.

>> I know robert mentioned it was going to be hard to do that (last
>> spring).  Any update? What can we do for erlang code that needs Erlang
>> macros and records defined in an hrl file?

>> --

>> You received this message because you are subscribed to the Google Groups
>> "Lisp Flavoured Erlang" group.
>> To post to this group, send email to
>> lisp-flavoured-erlang@googlegroups.com.
>> To unsubscribe from this group, send email to
>> lisp-flavoured-erlang+unsubscribe@googlegroups.com<lisp-flavoured-erlang%2B unsubscribe@googlegroups.com>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/lisp-flavoured-erlang?hl=en.

>  --
> You received this message because you are subscribed to the Google Groups
> "Lisp Flavoured Erlang" group.
> To post to this group, send email to
> lisp-flavoured-erlang@googlegroups.com.
> To unsubscribe from this group, send email to
> lisp-flavoured-erlang+unsubscribe@googlegroups.com<lisp-flavoured-erlang%2B unsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/lisp-flavoured-erlang?hl=en.

> I have a tool that transform hrl to lfe.

> http://github.com/cadar/hrl-to-lfe

> On Sun, Dec 20, 2009 at 3:05 AM, Jonathan Smith
> <jonathansmith...@gmail.com>wrote:

> > What I've been doing is rewriting the .hrl files as .lfe files (with
> > defrecord), and using include-file at the top of the .lfe files.

> > It is kind of a pain, but it ends up working out for the most part because
> > (IMO) the macros generated by defrecord are quite a bit
> > nicer to work with than the ones generated by the default Erlang records
> > stuff.

> > Are there other 'erlang' macros that would be difficult to replicate? or
> > are we talking about record stuff mostly?

> > Maybe we can startup a collection of rewritten .hrl files to make it a bit
> > less painful?

> > I'll happily donate the yaws_api.lfe that I have.

> > On Sat, Dec 19, 2009 at 3:06 PM, dysinger <t...@dysinger.net> wrote:

> >> The main roadblock for me in interop with erl code is hrl files.  Some
> >> of the core erlang libs use them (
> >>http://www.erlang.org/doc/man/file.html#read_file_info-1
> >> ) and they are _AFAIK_ unavailable inside LFE.

> >> I know robert mentioned it was going to be hard to do that (last
> >> spring).  Any update? What can we do for erlang code that needs Erlang
> >> macros and records defined in an hrl file?

> >> --

> >> You received this message because you are subscribed to the Google Groups
> >> "Lisp Flavoured Erlang" group.
> >> To post to this group, send email to
> >> lisp-flavoured-erlang@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> lisp-flavoured-erlang+unsubscribe@googlegroups.com<lisp-flavoured-erlang%2B unsubscribe@googlegroups.com>
> >> .
> >> For more options, visit this group at
> >>http://groups.google.com/group/lisp-flavoured-erlang?hl=en.

> >  --
> > You received this message because you are subscribed to the Google Groups
> > "Lisp Flavoured Erlang" group.
> > To post to this group, send email to
> > lisp-flavoured-erlang@googlegroups.com.
> > To unsubscribe from this group, send email to
> > lisp-flavoured-erlang+unsubscribe@googlegroups.com<lisp-flavoured-erlang%2B unsubscribe@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/lisp-flavoured-erlang?hl=en.