[erlang-questions] Finding inconsistencies in record definitions and pretty printing records

Vlad Dumitrescu vladdu55@REDACTED
Wed Oct 15 08:22:08 CEST 2008


On Tue, Oct 14, 2008 at 21:57, Joe Armstrong <erlang@REDACTED> wrote:
> On Tue, Oct 14, 2008 at 6:16 PM, mats cronqvist
>> "Joe Armstrong" <erlang@REDACTED> writes:
>>>     - compile record definitions into the modules
>>>       (uses a simple parse transform)
>>  this is the problematic bit. as has been hashed several times on
>>  this list, were record info exported (perhaps as a field in
>>  module_info), all kinds of cool things could be accomplished.
> It's not problematic - the parse transform in the enclosed code does
> exactly that.
> The enclosed code compiles record defs into the modules
> concerned - sets up the servers, detects module inconsitencies at run
> time and retrieves record definitions at run time *from any module*
> (not just the definition module).

This is cool!

Am I right that the "any module" above should be "any module compiled
with this parse_transform"? If yes, it restricts a little working with
legacy code, but it's still cool :-)


More information about the erlang-questions mailing list