Re: Free ELKS - {ROUTINE}.closed_operands signature

--- In [email protected], Eric Bezault  wrote:
> May I ask you why you are trying to use gec?

I'm currently building an Eiffel Package Manager (epm)
https://github.com/oligot/epm

This project allows me to explore new Eiffel possibilites, mainly:
* Void-safety: start with an empty project and make it Void-safe is quite easier
than migrating a non Void-safe project
* gec: start with an empty project and make it compile with gec is quite easier
than make it compile with a legacy project that only compiles with the ISE 
compiler
* as I'm also learning JavaScript, portability across various interpreters is
important: I'd like to know what this means to develop a portable Eiffel project

> The --ise option is to instruct gelint to use ISE's version of FreeELKS.

Didn't know about that option.
Maybe we could refactor the gelint code to use the argument library and provide
options descriptions (as in gec) so that gelint --help gives more help ?




------------------------------------

To Post a message, send it to:   [email protected]
To Unsubscribe, send a blank message to: [email protected]! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/gobo-eiffel/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/gobo-eiffel/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/