vote for MEP 104

Camilo Rueda crueda at atlas.puj.edu.co
Tue May 9 12:04:19 CEST 2006


I vote accept for MEP 104

Regards,

Camilo Rueda



>
> Today's Topics:
>
>    1. Re: MEP 104: Mozart release 1.3.2  - Please VOTE (Boriss Mejias)
>    2. Re: bug#1859 and autoconf (Boriss Mejias)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 03 May 2006 13:38:56 +0200
> From: Boriss Mejias <boris.mejias at uclouvain.be>
> Subject: Re: MEP 104: Mozart release 1.3.2  - Please VOTE
> To: hackers at mozart-oz.org
> Message-ID: <44589650.5020600 at uclouvain.be>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Dear hackers,
>
> Here is a more detailled list of the bug fixes that will be included in
> Mozart 1.3.2. One of the main points is that we are now compatible with
> gcc versions newer than 3.3. People is still complainning about this in
> the bug tracking system.
>
> o 1 Changes in Oz, Mozart libraries and UI
>
>     + 1.1 Copying of dictionaries was broken. Fixed. (Bug 1352)
>
>     + 1.2 Mozart added to the FSF directory. (Bug 1207)
>
>     + 1.3 Application.getGuiArgs now returns arguments as documented.
> (Bug 1691)
>
> o 2 Changes in the implementation that affect usability and performance
>
>     + 2.1 Oz Compiler
>
>       - Keyword 'native' has been removed from class
>         properties. This implies a change in the module Open in
>         contributions, fixing a runtime error. (Bug 1277)
>
>     + 2.2 Distribution Layer
>
>       - NewPort does not block anymore when using a distributed variable
>         for the stream. Currently, the builtin receives one input and one
>         output, but it should change to two outputs in a future release.
>         (Bug 1521).
>
>       - Problem with sockets generating 'segmentation fault' with P2PS is
>         fixed. (Bug 1304, 1339)
>
>       - Failed assertion in the Owner table fixed. (Bug 1461)
>
> o 3 Changes in the implementation that affect maintainability and
> portability
>
>       - Mozart 1.3.1 compiles with gcc up to version 3.3. Now it compiles
>         with gcc newer than 3.3 and up to 4.1
>
> o 4 More Bug Fixes:
>
>       - Documentation: 1419, 1660, 1479
>       - Error messages: 1429, 1816
>       - XML related: 1333
>       - GCC Compiler: 1636
>       - RPM building: 1649
>       - Reflect module: 1839
>       - FloatToString: 1869.
>
> cheers
> Boriss
>
> Peter Van Roy wrote:
>> Kevin Glynn wrote:
>>
>>>
>>> Dear Mozart Board,
>>>
>>> Boris has managed to create MEP 104 and it has been added to the mep
>>> website:
>>>    http://www.mozart-oz.org/meps/
>>>
>>> I am asking you to start the voting period now. Please vote quickly so
>>> that we can give Boris and Yves the required permissions asap.
>>>
>>>
>>> Kevin
>>>
>>
>> I vote accept for MEP 104.
>>
>> Peter
>>
>>
>> _________________________________________________________________________________
>>
>> mozart-hackers mailing list
>> mozart-hackers at ps.uni-sb.de
>> http://www.mozart-oz.org/mailman/listinfo/mozart-hackers
>>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 03 May 2006 13:48:57 +0200
> From: Boriss Mejias <boris.mejias at uclouvain.be>
> Subject: Re: bug#1859 and autoconf
> To: hackers at mozart-oz.org
> Message-ID: <445898A9.1090601 at uclouvain.be>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Boriss Mejias wrote:
>> Dear hackers,
>>
>> In the incoming bug reports, there is a contribution of Marc Hougardy
>> related to macosx running in intel (see bug#1859). It is about a small
>> fix in ozplatform.sh and emulator/configure. I have no way to test it,
>> but if nobody disagree I will commit it to the CVS.
>>
>> Then, a related issue is the reconf.sh script that is used to modify the
>> configure files using configure.in and aclocal.m4. It works with
>> autoconf 2.13, but it is not compatible with autoconf 2.5X, which are
>> the series that are mostly used now. One thing is that the -l option is
>> not valid any more, but I guess that the new one equivalent is -B. I
>> tried this, but I'm getting several warnings about variables set in
>> configure.in files, and finale the configure generated is not runnable.
>>
>> Is anyone familiar with the process of migrating from autoconf 2.13 to
>> 2.5X ?
>>
>> Does anybody disagree committing the fix to bug#1859?
>
> I'll commit the fix then, using autoconf 2.13.
>
> cheers
> Boriss
>
>>
>>
>> cheers
>> Boriss
>>
>>
>> _________________________________________________________________________________
>>
>> mozart-hackers mailing list
>> mozart-hackers at ps.uni-sb.de
>> http://www.mozart-oz.org/mailman/listinfo/mozart-hackers
>>
>
>
>
> ------------------------------
>
> _______________________________________________
> mozart-hackers mailing list
> mozart-hackers at ps.uni-sb.de
> http://www.ps.uni-sb.de/mailman/listinfo/mozart-hackers
>
>
> End of mozart-hackers Digest, Vol 29, Issue 3
> *********************************************
>






More information about the mozart-hackers mailing list