Ecf

[pgcrism]

Hello Eric,

Here is a pull request for the ecf files I talked about in a private mail.
Hope this helps.
Best regards,

Paul

[jocelyn]

I am not sure having -safe and -confident in the library's name is needed
I don't really mind, but it makes the name longer
But if this helps catching issue like using non void-safe lib in void-safe application why not.

[pgcrism]

Hello,

The library names mimic the file name. The intention is to recall the
characteristics of the ECF and prevent errors.

The name suffix have the following meaning:

• -safe : full void-safe library
• -confident: library settings adjusted so that a voidconfident system
  can be built. The libraries settings are - at least - full class
  checking and attached by default. When possible, the voidsafety level
  is 'initialization' instead of 'none'.

A voidconfident system has those general settings

• full class checking
• attached by default
• on demand void safety

Yes the names are long. It's the price I propose to pay for clarity.

Best regards,

PG Crismer

Le 21/11/2012 16:35, Jocelyn Fiat a écrit :

In library/gobo-core-confident.ecf:

@@ -0,0 +1,29 @@
+
+

•   <root all_classes="true"/>
  

•   <option warning="true" full_class_checking="true" is_attached_by_default="true" syntax="transitional">
  

•       <assertions precondition="true" postcondition="true" check="true" invariant="true" loop="true" supplier_precondition="true"/>
  

•   </option>
  

•   <setting name="console_application" value="true"/>
  

•   <library name="base-safe" location="$ISE_LIBRARY\library\base\base-safe.ecf"/>
  

I am not sure having -safe and -confident in the library's name is needed
I don't really mind, but it makes the name longer
But if this helps catching issue like using non void-safe lib in
void-safe application why not.

—
Reply to this email directly or view it on GitHub
https://github.com/gobo-eiffel/gobo/pull/3/files#r2195200.

[oligot]

Hi @ebezault,

Is there a reason why this pull request hasn't been merged yet ?

[oligot]

Note that there is an open discussion in the Gobo mailing list.
Here is the replay from Eric:
http://tech.groups.yahoo.com/group/gobo-eiffel/message/1823

In the meantime, the ecf files are available in another Git repository:
https://github.com/oligot/gobo-ecf

[gchauvet]

Does this pull request still in activity ?

[ebezault]

It's just that I hadn't have time yet to work on the issue.
I didn't pull the suggestion as-is because I don't want to end up with many ECF files for the same code depending on the compilation options. This goes against the spirit of ECF and Xace.
I would prefer to improve gexace so that it can generate better ECF files, and then have only one Xace file per library from which each user would be able to generate his own custom ECf file at will.