[erlang-questions] misultin on erlang R13B04?

Joseph Wayne Norton <>
Mon Sep 5 18:04:12 CEST 2011


One other suggestion.  If you are using rebar as your build tool, the platform_define directive works quite well.

Here is an example for "old_inets":

https://github.com/norton/ubf-jsonrpc/blob/master/rebar.config

https://github.com/norton/ubf-jsonrpc/blob/master/src/ubf_jsonrpc_inets_httpc_simple.erl

thanks,

- Joe N

On 2011/09/06, at 0:57, Kostis Sagonas wrote:

> On 09/05/11 18:16, Roberto Ostinelli wrote:
>> On Mon, Sep 5, 2011 at 3:33 PM, Robert Virding
>> <
>> <mailto:>> wrote:
>> 
>>    ------------------------------------------------------------------------
>> 
>>        However, since I do plan to add support for previous versions
>>        [misultin does support R13xx except for type and specs
>>        definitions], can someone point me in a right direction for how
>>        to do so?
>> 
>> 
>>    Remove all type and spec definitions. :-)
>> 
>> 
>> ..seriously? i'm quite fond in using these, as they add to methodology
>> and tracking of own code. also, with tools such as PropEr there's an
>> additional good reason to add them. id' rather add a >=R14 spec to
>> misultin than to remove specs.
> 
> Good choice! :)
> 
>> however, ideally, since Kostis has pointed out there are ways to have
>> them working on different Erlang versions, I'd like to hear how to do this.
> 
> I suggested looking how it's done at the 'configure' of Scalaris.
> 
> Its code is here: http://scalaris.googlecode.com/svn/trunk/configure
> 
> Search for e.g. gb_tree() or DIALYZER to see how to write (portions of) a configure script that allows to generate appropriate defines for various types that have become built-ins or changed status between different OTP versions.
> 
> ____Kostis
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions

Joseph Wayne Norton





More information about the erlang-questions mailing list