gobo-eiffel-develop — Development discussions

[gobo-eiffel-develop] Which version of Gobo does compile out-of-the-box with ISE 6.7 ?

[CRISMER Paul-G. <Pau...@gr...>]

Hello,
 
Which version of Gobo does compile out-of-the-box with ISE 6.7 ?
Version 3.9 does not.
 
Which version should I choose? 
I favor a version from the Gobo repository instead of the one packed by
ISE.
 
Thank you for the help,
 
Best regards,
 
Paul G. Crismer
 

***** Disclaimer *****
http://www.groupes.be/1_mail-disclaimer.htm

Re: [gobo-eiffel-develop] Turning off CATCALL detection with gec

[Eric B. <er...@go...>]

On 12/19/2010 10:15 AM, Colin Paul Adams wrote:
>>>>>> "Eric" == Eric Bezault<er...@go...>  writes:
>
>      Eric>  The error reported is not a CAT-call, it's a flat Degree 3
>      Eric>  error.  You should get the same error with EiffelStudio is you
>      Eric>  set full_class_checking in the ECF file.
>
> I do.
> Is there a way of specifying this in an xace file?

The following in the Xace file:

    <option name="full_class_checking" value="true"/>

will be translated to the corresponding option
in the genrated ECF file.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] Turning off CATCALL detection with gec

[Colin P. A. <co...@co...>]

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> The error reported is not a CAT-call, it's a flat Degree 3
    Eric> error.  You should get the same error with EiffelStudio is you
    Eric> set full_class_checking in the ECF file.

I do.
Is there a way of specifying this in an xace file?
-- 
Colin Adams
Preston Lancashire
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Re: [gobo-eiffel-develop] Turning off CATCALL detection with gec

[Eric B. <er...@go...>]

On 12/18/2010 11:39 AM, Colin Paul Adams wrote:
>>>>>> "Eric" == Eric Bezault<er...@go...>  writes:
>
>      Eric>  I think that this command-line option is independent of the
>      Eric>  type of Eiffel config file passed as input.
>
>      Eric>  But I'm not sure I understand the problem. Are you saying that
>      Eric>  gec reports the CAT-call error at compilation time despite the
>      Eric>  fact that you use the command-line option --catcall=no?
>
> Yes.

The error reported is not a CAT-call, it's a flat Degree 3 error.
You should get the same error with EiffelStudio is you set
full_class_checking in the ECF file.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

[gobo-eiffel-develop] [Colin Paul Adams] Re: Turning off CATCALL detection with gec

[Colin P. A. <co...@co...>]

I forgot to copy to the list:

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> I think that this command-line option is independent of the
    Eric> type of Eiffel config file passed as input.

    Eric> But I'm not sure I understand the problem. Are you saying that
    Eric> gec reports the CAT-call error at compilation time despite the
    Eric> fact that you use the command-line option --catcall=no? 

Yes.

    Eric> that if you use --catcall=no at compilation time, the error
    Eric> will nevertheless be reported at run-time.

I'd better include the complete example:

build.geant:

<?xml version="1.0"?>

<project name="grass" default="help">

        <description>
                description: "Eiffel Ant file for 'grass'"
                system: "Covariance typing demonstration - from Eiffel FAQ LCON"
                copyright: "Copyright (c) 2010, Colin Adams"
                license: "GPL v3"
                date: "$Date$"
                revision: "$Revision$"
        </description>

        <inherit>
                <parent location="${GOBO}/misc/eiffel.eant">
                        <redefine target="init_system"/>
                </parent>
        </inherit>


<!-- Implementation -->

        <target name="init_system">             
	 <set name="system" value="grass"/>
	 <set name="system_dir" value="."/>
        </target>

</project>

system.xace:

<?xml version="1.0"?>

<system name="grass">
        <description>
            system: "Covariance typing demonstration - from Eiffel FAQ LCON"
            copyright: "Copyright (c) 2010, Colin Adams"
            license: "GPL v3"
            date: "$Date$"
            revision: "$Revision$"
        </description>

        <root class="ROOT" creation="make"/>
        <option name="console_application" value="true"/>
        <option if="${GOBO_EIFFEL}=ge">
                <option if="${BOEHM_GC}">
                        <option name="garbage_collector" value="boehm"/>
                </option>
        </option>
        <option unless="${DEBUG}">
                <option name="assertion" value="none"/>
                <option name="finalize" value="true"/>
        </option>
        <option if="${DEBUG}">
               <option name="assertion" value="all"/>
                <option name="finalize" value="false"/>
        </option>

        <cluster name="grass" location="."/>

        <mount location="${GOBO}/library/kernel/library.xace"/>
        <mount location="${GOBO}/library/structure/library.xace"/>
        <mount location="${GOBO}/library/kernel.xace"/>
</system>


root.e:

class ROOT

create

	make

feature {NONE} -- Initialization

	make is
			-- Run the system without covariance.
		local
			l_herb1, l_herb2: HERBIVORE
			l_plant: PLANT
			l_grass: GRASS
			l_cow: COW
		do
			create l_plant
			create l_grass
			create l_herb1.make
			create l_herb2.make
			l_herb1.eat (l_plant)
			l_herb2.eat (l_grass)
				-- test1, so far, so good
			create l_cow
			l_cow.eat (l_grass)
			-- this is statically rejected - no problems: l_cow.eat (l_plant)
				-- test2, so far, so good
			l_herb1.diet.put_last (l_plant)
			l_herb1.diet.put_last (l_grass)
			l_herb1.digest
				-- no problem - herbivores can eat grass
			l_cow.diet.put_last (l_plant)
			l_cow.diet.put_last (l_grass)
			l_cow.digest
			
		end

end

plant.e:

class PLANT

end

grass.e:

class GRASS

inherit

	PLANT

end

herbivore.e:

class HERBIVORE

create

	make

feature {NONE} -- Initialization

	make is
			-- Initialize.
		do
			create diet.make_default
		end

feature -- Access

	diet: DS_ARRAYED_LIST [PLANT]
			-- Items we can eat

feature -- Basic operations
	
	eat (a_food: PLANT) is
			-- Say what we are eating
		do
			print ("Eating " + a_food.generator + "%N")		
		end


	digest is
			-- Eat entire diet (greedy!).
		local
			l_cursor: DS_ARRAYED_LIST_CURSOR [PLANT]
		do
			from
				l_cursor := diet.new_cursor
				l_cursor.start
			until
				l_cursor.after
			loop
				eat (l_cursor.item)
				l_cursor.forth
			end
		end

invariant
	
	diet_not_void: diet /= Void

end

cow.e:

class COW                  

inherit                  

	HERBIVORE             
      redefine eat end
	
feature -- Basic operations

	eat (a_food: GRASS) is
			-- <Precursor>
		do
			Precursor (a_food)
		end

end

-- 
Colin Adams
Preston Lancashire
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Re: [gobo-eiffel-develop] Turning off CATCALL detection with gec

[Eric B. <er...@go...>]

I think that this command-line option is independent
of the type of Eiffel config file passed as input.

But I'm not sure I understand the problem. Are you
saying that gec reports the CAT-call error at compilation
time despite the fact that you use the command-line option
--catcall=no? Note that if you use --catcall=no at
compilation time, the error will nevertheless be reported
at run-time.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com


On 12/18/2010 11:04 AM, Colin Paul Adams wrote:
> According to the gec command-line help, there is an option
> --catcall=no|error|warning with the default being warning.
>
> Does this only apply to ace input, rather than xace? I seem to get
> errors that ISE 6.7 passes (incorrectly), and results in a call-on-void
> target at runtime.
>
> The (correct) error I get from gec is:
>
> [VUAR-2] class COW (HERBIVORE,40,5): the 1-th actual argument (of type 'PLANT')
> does not conform to the corresponding formal argument (of type 'GRASS')
> of feature `eat'.
>
> This is using a test based on the incomplete example in the LCON section of the
> Eiffel FAQ.
>
> Are there some categories of CATCALL that gec always reports, regardless
> of the setting?

[gobo-eiffel-develop] Turning off CATCALL detection with gec

[Colin P. A. <co...@co...>]

According to the gec command-line help, there is an option
--catcall=no|error|warning with the default being warning.

Does this only apply to ace input, rather than xace? I seem to get
errors that ISE 6.7 passes (incorrectly), and results in a call-on-void
target at runtime. 

The (correct) error I get from gec is:

[VUAR-2] class COW (HERBIVORE,40,5): the 1-th actual argument (of type 'PLANT')
does not conform to the corresponding formal argument (of type 'GRASS')
of feature `eat'. 

This is using a test based on the incomplete example in the LCON section of the
Eiffel FAQ.

Are there some categories of CATCALL that gec always reports, regardless
of the setting?
-- 
Colin Adams
Preston Lancashire
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Re: [gobo-eiffel-develop] KL_EXECUTION_ENVIRONMENT does not inherit from EXECUTION_ENVIRONMENT anymore.

[Eric B. <er...@go...>]

On 10/18/2010 11:20 AM, CRISMER Paul-Georges wrote:
> Hello,
>
> As of GOBO 3.9, KL_EXECUTION_ENVIRONMENT inherits from
> EXECUTION_ENVIRONMENT.
> The features 'put' and 'launch' are accessible.
>
> On the trunk, KL_EXECUTION_ENVIRONMENT uses delegation.

In fact it should have always used delegation. The idea was
not to support all features from ISE's EXECUTION_ENVIRONMENT
in Gobo, but to make available in Gobo some of the features which
were or are likely to be provided by all Eiffel compilers.
That's why it uses delegation. That's more or less what
EiffelVision2 does. EV_ classes don't inherit from the WEL
or GTK classes.

> How can we use the 'put' and 'launch' features?
> Are they available in other gobo classes?

Instead of `put', you can try to use `set_variable_value'
from KL_EXECUTION_ENVIRONMENT. There is no equivalent of
`launch' in Gobo. The closest in `execute' in KL_SHELL_COMMAND,
but it's not asynchronous.

Note that as of today, Gobo only supports EiffelStudio and
gec. And both use FreeELKS. So you might want to try to use
EXECUTION_ENVIRONMENT directly.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

[gobo-eiffel-develop] KL_EXECUTION_ENVIRONMENT does not inherit from EXECUTION_ENVIRONMENT anymore.

[CRISMER Paul-G. <Pau...@gr...>]

Hello,

As of GOBO 3.9, KL_EXECUTION_ENVIRONMENT inherits from
EXECUTION_ENVIRONMENT.
The features 'put' and 'launch' are accessible.

On the trunk, KL_EXECUTION_ENVIRONMENT uses delegation.

How can we use the 'put' and 'launch' features?
Are they available in other gobo classes?

Thank you for the help,
Best regards,

Paul G. Crismer

***** Disclaimer *****
http://www.groupes.be/1_mail-disclaimer.htm

[gobo-eiffel-develop] GOBO trunk and Ise 6.6

[CRISMER Paul-G. <Pau...@gr...>]

Hello,

What is the status of the current git trunk :
- Does it support the new syntax (ISE 6.6 'standard')
- Is it compatible with void-safe mode
- What it the difference between Gobo-git-trunk and the gobo library
provided with Ise 6.6 ?

Thank you for your help,
Best regards,

Paul G. Crismer

***** Disclaimer *****
http://www.groupes.be/1_mail-disclaimer.htm

Re: [gobo-eiffel-develop] GOBO trunk and Ise 6.6

[CRISMER Paul-G. <Pau...@gr...>]

Thank you Eric for your answer,

>I don't know whether the version in ISE 6.6 includes recent
developments from Gobo-git-trunk. On the other hand 
>it is likely that the version in ISE 6.6 will have been modified to be
void-safe (or at least more void-safe than > the version in
Gobo-git-trunk).

Do you mean that for the moment void safety is not in the roadmap of
Gobo?

Best regards,

Paul G. Crismer

***** Disclaimer *****
http://www.groupes.be/1_mail-disclaimer.htm

Re: [gobo-eiffel-develop] GOBO trunk and Ise 6.6

[Eric B. <er...@go...>]

On 9/16/2010 3:02 PM, CRISMER Paul-Georges wrote:
> Thank you Eric for your answer,
>
>> I don't know whether the version in ISE 6.6 includes recent
> developments from Gobo-git-trunk. On the other hand
>> it is likely that the version in ISE 6.6 will have been modified to be
> void-safe (or at least more void-safe than>  the version in
> Gobo-git-trunk).
>
> Do you mean that for the moment void safety is not in the roadmap of
> Gobo?

Not in the near future.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] GOBO trunk and Ise 6.6

[Eric B. <er...@go...>]

On 9/16/2010 2:29 PM, CRISMER Paul-Georges wrote:
> Hello,
>
> What is the status of the current git trunk :
> - Does it support the new syntax (ISE 6.6 'standard')

I think so.

> - Is it compatible with void-safe mode

No.

> - What it the difference between Gobo-git-trunk and the gobo library
> provided with Ise 6.6 ?

I don't know whether the version in ISE 6.6 includes recent developments
from Gobo-git-trunk. On the other hand it is likely that the version
in ISE 6.6 will have been modified to be void-safe (or at least more
void-safe than the version in Gobo-git-trunk).

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

Re: [gobo-eiffel-develop] GEC persistence closure & debugger

[Wolfgang J. <wj...@so...>]

On 06/17/10 16:41, Eric Bezault wrote:
> Cheng-Chang Wu wrote:
>    
>> Now the git repository works.
>>      
> Thank you for letting us know. It works for me as well.
>
>    
Fine, so the question is what do you plan to do with the stuff?

WJ

-- 
Dr. Wolfgang Jansen
University of Potsdam, Germany
Institute of Computer Science
Tel: +49 331 / 977 3047
mailto: wj...@so...

Re: [gobo-eiffel-develop] GEC persistence closure & debugger

[Wolfgang J. <wj...@so...>]

On 06/17/10 13:50, Cheng-Chang Wu wrote:
> Now the git repository works.
> Thanks.
>
>
>
> ----- ­ì©l«H¥ó ----
> ±H¥óªÌ¡G Wolfgang Jansen<wj...@so...>
> ¦¬¥óªÌ¡G gob...@li...
> ±H¥ó¤é´Á¡G 2010/6/1 (¤G) 5:31:51 PM
> ¥D¡@¦®¡G Re: [gobo-eiffel-develop] GEC persistence closure&  debugger
>
> On 05/31/10 23:32, Cheng-Chang Wu wrote:
>    
>> Hello Wolfgang,
>>
>> the git repository doesn't work for me.
>>
>> $git clone http://www.cs.uni-potsdam.de/~wjansen/gobo-git/
>>
>> Initialized empty Git repository in /home/ccwu/src/git/gobo-dbg/gobo-git/.git/
>> fatal: http://www.cs.uni-potsdam.de/~wjansen/gobo-git//info/refs not found: did you run git update-server-info on the server?
>>
>>
>>      
> No, I didn't. The point is that I am not very familiar with git and,
> worse, git manual
> and git implementation differ very much. I was not aware of such things as
> "git-update-server-info". Now, I run the command but my impression is
> that nothing happened.
> Surely, I will need some help on git.
>
> WJ
>
>
>
>
>
>
>    
Sorry for the trouble I caused.

BTW, it was necessary that I installed a new git version,
and even this version differs from the description.
So, I was not sure that it works. Thanks for the message.

WJ

-- 
Dr. Wolfgang Jansen
University of Potsdam, Germany
Institute of Computer Science
Tel: +49 331 / 977 3047
mailto: wj...@so...

Re: [gobo-eiffel-develop] GEC persistence closure & debugger

[Eric B. <er...@go...>]

Cheng-Chang Wu wrote:
> Now the git repository works.

Thank you for letting us know. It works for me as well.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com


> Thanks.
> 
> 
> 
> ----- 原始信件 ----
> 寄件者： Wolfgang Jansen <wj...@so...>
> 收件者： gob...@li...
> 寄件日期： 2010/6/1 (二) 5:31:51 PM
> 主　旨： Re: [gobo-eiffel-develop] GEC persistence closure & debugger
> 
> On 05/31/10 23:32, Cheng-Chang Wu wrote:
>> Hello Wolfgang,
>>
>> the git repository doesn't work for me.
>>
>> $git clone http://www.cs.uni-potsdam.de/~wjansen/gobo-git/
>>
>> Initialized empty Git repository in /home/ccwu/src/git/gobo-dbg/gobo-git/.git/
>> fatal: http://www.cs.uni-potsdam.de/~wjansen/gobo-git//info/refs not found: did you run git update-server-info on the server?
>>
>>    
> No, I didn't. The point is that I am not very familiar with git and, 
> worse, git manual
> and git implementation differ very much. I was not aware of such things as
> "git-update-server-info". Now, I run the command but my impression is 
> that nothing happened.
> Surely, I will need some help on git.
> 
> WJ

Re: [gobo-eiffel-develop] GEC persistence closure & debugger

[Cheng-Chang Wu <che...@ya...>]

Now the git repository works.
Thanks.



----- 原始信件 ----
寄件者： Wolfgang Jansen <wj...@so...>
收件者： gob...@li...
寄件日期： 2010/6/1 (二) 5:31:51 PM
主　旨： Re: [gobo-eiffel-develop] GEC persistence closure & debugger

On 05/31/10 23:32, Cheng-Chang Wu wrote:
> Hello Wolfgang,
>
> the git repository doesn't work for me.
>
> $git clone http://www.cs.uni-potsdam.de/~wjansen/gobo-git/
>
> Initialized empty Git repository in /home/ccwu/src/git/gobo-dbg/gobo-git/.git/
> fatal: http://www.cs.uni-potsdam.de/~wjansen/gobo-git//info/refs not found: did you run git update-server-info on the server?
>
>    
No, I didn't. The point is that I am not very familiar with git and, 
worse, git manual
and git implementation differ very much. I was not aware of such things as
"git-update-server-info". Now, I run the command but my impression is 
that nothing happened.
Surely, I will need some help on git.

WJ


      

Re: [gobo-eiffel-develop] GEC persistence closure & debugger

[Wolfgang J. <wj...@so...>]

On 05/31/10 23:32, Cheng-Chang Wu wrote:
> Hello Wolfgang,
>
> the git repository doesn't work for me.
>
> $git clone http://www.cs.uni-potsdam.de/~wjansen/gobo-git/
>
> Initialized empty Git repository in /home/ccwu/src/git/gobo-dbg/gobo-git/.git/
> fatal: http://www.cs.uni-potsdam.de/~wjansen/gobo-git//info/refs not found: did you run git update-server-info on the server?
>
>    
No, I didn't. The point is that I am not very familiar with git and, 
worse, git manual
and git implementation differ very much. I was not aware of such things as
"git-update-server-info". Now, I run the command but my impression is 
that nothing happened.
Surely, I will need some help on git.

WJ

----- ­ì©l«H¥ó ----
±H¥óªÌ¡G Wolfgang Jansen<wj...@so...>
¦¬¥óªÌ¡G Gobo Developers Mailing List<gob...@li...>
±H¥ó¤é´Á¡G 2010/6/1 (¤G) 2:02:19 AM
¥D¡@¦®¡G [gobo-eiffel-develop] GEC persistence closure&  debugger

Hello Eric and all GOBO/GEC developers,

some time ago i've announced development of persistence closure (i.e.
class STORABLE)
and a debugger for the GEC. It took some time to get stable version
(in particular, treatment of agents was --and is-- rather terrible).

Now, I think, the stuff can be published: you will find it in
git-repository
   http://www.cs.uni-potsdam.de/~wjansen/gobo-git
and there in branch "debugger" (the "master" branch is that from
SourceForge).
Is this location accessible? Should I prepare the stuff a different way?

For those of you interested to know what has been done, most differences
to the "master" branch are contained and described in git-version
    9003cd425affac20f946d7803e2782dfd261fbe7 .
Later versions are merely fine tuning.

To use the new things you need to re-install the GEC.
Precisely, you must compile GEC twice: first using an existing compiler
and then using the just obtained, somewhat extended compiler.
Other tools don't need to be re-installed.
Forthcoming re-installations will need only one compilation
if the extended compiler can be used.

User manuals are in directories
    doc/persistence/persist.pdf
    doc/debugger/debug.pdf
of the repository.

Enjoy GEC-debugging!
WJ




-- 
Dr. Wolfgang Jansen
University of Potsdam, Germany
Institute of Computer Science
Tel: +49 331 / 977 3047
mailto: wj...@so...

Re: [gobo-eiffel-develop] GEC persistence closure & debugger

[Cheng-Chang Wu <che...@ya...>]

Hello Wolfgang,

the git repository doesn't work for me.

$git clone http://www.cs.uni-potsdam.de/~wjansen/gobo-git/

Initialized empty Git repository in /home/ccwu/src/git/gobo-dbg/gobo-git/.git/
fatal: http://www.cs.uni-potsdam.de/~wjansen/gobo-git//info/refs not found: did you run git update-server-info on the server?



----- 原始信件 ----
寄件者： Wolfgang Jansen <wj...@so...>
收件者： Gobo Developers Mailing List <gob...@li...>
寄件日期： 2010/6/1 (二) 2:02:19 AM
主　旨： [gobo-eiffel-develop] GEC persistence closure & debugger

Hello Eric and all GOBO/GEC developers,

some time ago i've announced development of persistence closure (i.e. 
class STORABLE)
and a debugger for the GEC. It took some time to get stable version
(in particular, treatment of agents was --and is-- rather terrible).

Now, I think, the stuff can be published: you will find it in 
git-repository
  http://www.cs.uni-potsdam.de/~wjansen/gobo-git
and there in branch "debugger" (the "master" branch is that from 
SourceForge).
Is this location accessible? Should I prepare the stuff a different way?

For those of you interested to know what has been done, most differences
to the "master" branch are contained and described in git-version
   9003cd425affac20f946d7803e2782dfd261fbe7 .
Later versions are merely fine tuning.

To use the new things you need to re-install the GEC.
Precisely, you must compile GEC twice: first using an existing compiler
and then using the just obtained, somewhat extended compiler.
Other tools don't need to be re-installed.
Forthcoming re-installations will need only one compilation
if the extended compiler can be used.

User manuals are in directories
   doc/persistence/persist.pdf
   doc/debugger/debug.pdf
of the repository.

Enjoy GEC-debugging!
WJ

-- 
Dr. Wolfgang Jansen
University of Potsdam, Germany
Institute of Computer Science
Tel: +49 331 / 977 3047
mailto: wj...@so...


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

_______________________________________________
gobo-eiffel-develop mailing list
gob...@li...
https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop



      

[gobo-eiffel-develop] GEC persistence closure & debugger

[Wolfgang J. <wj...@so...>]

Hello Eric and all GOBO/GEC developers,

some time ago i've announced development of persistence closure (i.e. 
class STORABLE)
and a debugger for the GEC. It took some time to get stable version
(in particular, treatment of agents was --and is-- rather terrible).

Now, I think, the stuff can be published: you will find it in 
git-repository
   http://www.cs.uni-potsdam.de/~wjansen/gobo-git
and there in branch "debugger" (the "master" branch is that from 
SourceForge).
Is this location accessible? Should I prepare the stuff a different way?

For those of you interested to know what has been done, most differences
to the "master" branch are contained and described in git-version
   9003cd425affac20f946d7803e2782dfd261fbe7 .
Later versions are merely fine tuning.

To use the new things you need to re-install the GEC.
Precisely, you must compile GEC twice: first using an existing compiler
and then using the just obtained, somewhat extended compiler.
Other tools don't need to be re-installed.
Forthcoming re-installations will need only one compilation
if the extended compiler can be used.

User manuals are in directories
   doc/persistence/persist.pdf
   doc/debugger/debug.pdf
of the repository.

Enjoy GEC-debugging!
WJ

-- 
Dr. Wolfgang Jansen
University of Potsdam, Germany
Institute of Computer Science
Tel: +49 331 / 977 3047
mailto: wj...@so...

Re: [gobo-eiffel-develop] CECIL

[Hayden S. <hay...@gm...>]

Thanks for that Eric,

I've grabbed a copy of your lexer and parser grammars from the site
and have modified them for use with Flex and Bison. This is a short
term approach, but it appears to be working.

On Sun, May 30, 2010 at 12:30 AM, Eric Bezault <er...@go...> wrote:
> Hello Hayden,
>
> Cecil is not on the priority list in the Gobo project.
>
> Cecil is used to call Eiffel code from C. So Eiffel code compiled
> with gec cannot be called from a C program. But it can be called
> from C code which is itself called from an Eiffel program. So if
> your program is in Eiffel, before calling the C code you can pass
> to C the address of the Eiffel functions you want to call back
> from C, using Eiffel's $ operator.
>
> On the other hand, if your program is in C, and what you want to
> do is to use the Eiffel code making up the Gobo compiler, you can
> compile the Gobo Eiffel code with ISE's EiffelStudio compiler, and
> then use Cecil (which is supported when the Eiffel code is compiled
> with EiffelStudio) to call Gobo Eiffel's code from C.
>
> --
> Eric Bezault
> mailto:er...@go...
> http://www.gobosoft.com
>
>
> Hayden Smith wrote:
>>
>> I've been putting together a plugin for Qt Creator for working with Gobo
>> Eiffel projects. So far, I've just implemented basic highlighting of
>> reserved keywords, predefined keywords and types defined in ELKS.
>>
>> The next step is to form an abstract syntax tree so I can implement
>> autocompletion and other context-dependent actions. Ideally, I would like to
>> use classes from gec to do this and figured that the best way to work with
>> them was via CECIL. The only reference I could find though was that it
>> hadn't been implemented yet. Is this a feature that's high on the priority
>> list, or are there any other ways of integrating the gec classes that I
>> could use? (Qt is written in C++)
>>
>> Qt uses MIME types to associate editors with file extension patterns with
>> specific editors. I couldn't find a specific type for Eiffel source code, so
>> I just used 'application/eiffel-source'. Is there a specific MIME type I can
>> use or would anyone like to suggest an alternative?
>
>
>
>

Re: [gobo-eiffel-develop] CECIL

[Eric B. <er...@go...>]

Hello Hayden,

Cecil is not on the priority list in the Gobo project.

Cecil is used to call Eiffel code from C. So Eiffel code compiled
with gec cannot be called from a C program. But it can be called
from C code which is itself called from an Eiffel program. So if
your program is in Eiffel, before calling the C code you can pass
to C the address of the Eiffel functions you want to call back
from C, using Eiffel's $ operator.

On the other hand, if your program is in C, and what you want to
do is to use the Eiffel code making up the Gobo compiler, you can
compile the Gobo Eiffel code with ISE's EiffelStudio compiler, and
then use Cecil (which is supported when the Eiffel code is compiled
with EiffelStudio) to call Gobo Eiffel's code from C.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com


Hayden Smith wrote:
> I've been putting together a plugin for Qt Creator for working with Gobo Eiffel projects. So far, I've just implemented basic highlighting of reserved keywords, predefined keywords and types defined in ELKS.
> 
> The next step is to form an abstract syntax tree so I can implement autocompletion and other context-dependent actions. Ideally, I would like to use classes from gec to do this and figured that the best way to work with them was via CECIL. The only reference I could find though was that it hadn't been implemented yet. Is this a feature that's high on the priority list, or are there any other ways of integrating the gec classes that I could use? (Qt is written in C++)
> 
> Qt uses MIME types to associate editors with file extension patterns with specific editors. I couldn't find a specific type for Eiffel source code, so I just used 'application/eiffel-source'. Is there a specific MIME type I can use or would anyone like to suggest an alternative?

[gobo-eiffel-develop] CECIL

[Hayden S. <hay...@gm...>]

I've been putting together a plugin for Qt Creator for working with Gobo Eiffel projects. So far, I've just implemented basic highlighting of reserved keywords, predefined keywords and types defined in ELKS.

The next step is to form an abstract syntax tree so I can implement autocompletion and other context-dependent actions. Ideally, I would like to use classes from gec to do this and figured that the best way to work with them was via CECIL. The only reference I could find though was that it hadn't been implemented yet. Is this a feature that's high on the priority list, or are there any other ways of integrating the gec classes that I could use? (Qt is written in C++)

Qt uses MIME types to associate editors with file extension patterns with specific editors. I couldn't find a specific type for Eiffel source code, so I just used 'application/eiffel-source'. Is there a specific MIME type I can use or would anyone like to suggest an alternative?

Cheers!

Re: [gobo-eiffel-develop] [gobo-eiffel] Re: Using "transitional syntax" clusters (ISE 6.5) and gexace

[CRISMER Paul-G. <Pau...@gr...>]

Hi Eric,

Thank you very much for your help.
Best regards,

Paul G. Crismer 

-----Original Message-----
From: Eric Bezault [mailto:er...@go...] 
Sent: dimanche 28 février 2010 18:57
To: gob...@ya...
Cc: Gobo Developers Mailing List
Subject: Re: [gobo-eiffel-develop] [gobo-eiffel] Re: Using "transitional syntax" clusters (ISE 6.5) and gexace

Hi Paul,

pgcrism wrote:
> What class should I modify to be able to specify such an option?
> If it's possible, I would like to adapt gexace and then propose my modifications to the GOBO project.

I just put in the git repository some documentation explaining how to add a new option to Xace. It's in $GOBO/doc/tools/new_xace_options.html.

As a way to be sure that nothing was missing, I also implemented the new option 'syntax' while writing the documentation. It is also available in the git repository.

--
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
gobo-eiffel-develop mailing list
gob...@li...
https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop

***** Disclaimer *****
http://www.groupes.be/1_mail-disclaimer.htm

Re: [gobo-eiffel-develop] [gobo-eiffel] Re: Using "transitional syntax" clusters (ISE 6.5) and gexace

[Eric B. <er...@go...>]

Hi Paul,

pgcrism wrote:
> What class should I modify to be able to specify such an option?
> If it's possible, I would like to adapt gexace and then propose my modifications to the GOBO project.

I just put in the git repository some documentation
explaining how to add a new option to Xace. It's in
$GOBO/doc/tools/new_xace_options.html.

As a way to be sure that nothing was missing, I also
implemented the new option 'syntax' while writing the
documentation. It is also available in the git repository.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com