Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] YASE, back to the roots

Hi again,

I am sorry to delay the definite answer to your problem to next Wednesday,
when other members of the team come back from holidays. The problem you
faced is directly linked to some corrections we made on our memory model,
and there are issues I cannot decide to solve one way or another by myself.

Sorry for the inconvenience, we will send you a patch asap next week.


On Thu, Oct 30, 2008 at 9:51 AM, Pascal Cuoq <> wrote:

>  I think we'll have to patch the current release to overcome this problem.
>> If so, we will announce it on this list soon.
> Indeed, the release was a little bit rushed, but it's okay
> because the version is clearly labeled as "beta" :)
> I would like to take this opportunity to encourage plug-in
> developers to work with the users of their plug-ins
> to make the next iteration of Frama-C (to be released in
> the next few days) as stable as possible.
> Frama-C is Open Source and Frama-C's users
> are bright and motivated people.
> It is probably a good, efficient way
> to work to send them patches in order to
> fix the problem that is blocking them and allow them
> to further their tests, so that the next release may work
> really well for what is supposed to work already.
> Thanks to everyone on this list for their contributions.
> Pascal

-------------- next part --------------
An HTML attachment was scrubbed...