RE: Binary files

Hello Eric!

Ah yes. When a library has been precompiled this is clearly the best option. When dealing with other repositories though, this is not an option. Unless the class you seek has been compiled, it cannot reveal its relationships (that psychic thing again). Then the grep-like method is about all there is.
Clearly, precompilation has a major value beyond convenience and should be the default case.

R

==================================================
Roger F. Osmond
----------------------------------------
Amalasoft Corporation
273 Harwood Avenue
Littleton, MA 01460

> -------- Original Message --------
> Subject: Re: [eiffel_software] Binary files
&gt; From: Eric Bezault < ericb%40gobosoft.com">ericbgobosoft.com>
> Date: Thu, March 22, 2007 11:28 am
> To: eiffel_software%40yahoogroups.com">eiffel_softwareyahoogroups.com
>
>
>
> rfo%40amalasoft.com">rfoamalasoft.com wrote:
&gt; > While English is my native language (and I am almost fluent in it), I confess that I too fail to deduce the name of the class I seek. To get around my lack of psychic powers, I use wildcards in the class pull-down menu in estudio. In your case, type in "*FILE*" and you will see what you are trying to find. It's not foolproof but the class libraries do follow reasonble naming conventions most of the time.
&gt;
> I usually don't rely on grep (e.g. *FILE*) to find specialized classes.
> I rather take the general class (here class FILE) and ask EiffelStudio
> for its descendants.
>
> --
> Eric Bezault
> mailto: ericb%40gobosoft.com">ericbgobosoft.com
> http://www.gobosoft.com
>

Messages in this topic (0) Reply (via web post) | Start a new topic

.

rfo%40amalasoft.com">rfoamalasoft.com wrote:
&gt; Ah yes. When a library has been precompiled this is clearly the best option. When dealing with other repositories though, this is not an option. Unless the class you seek has been compiled, it cannot reveal its relationships (that psychic thing again). Then the grep-like method is about all there is.
> Clearly, precompilation has a major value beyond convenience and should be the default case.

At work I don't have this problem with whether classes are compiled
or not. We use a Eiffel tool similar to EiffelStudio built on top
of the Gobo Eiffel code analysis framework which doesn't suffer from
this problem. All classes are fully browsable, regardless of whether
they are compiled or not.

At home I always have an EiffelStudio project with all classes
compiled (using NONE as root class), so that I can browse the
classes without restriction. This is explained in this LearnLet:

http://www.eiffel.com/developers/learning_maps/Training/Learnlets/GettingTheRightView/player.html

I prefer to have such an EiffelStudio project always available
(in addition to the project I work on), rather than relying on
grep. Had the class been called RAW_MEDIUM instead of RAW_FILE,
I would have found it, whereas *FILE* would not. Of course this
assumes that the library was sufficiently well designed to get
the inheritance graph right, which is not obvious if on the
other hand we don't trust the way class names were chosen.

--
Eric Bezault
mailto: ericb%40gobosoft.com">ericbgobosoft.com
http://www.gobosoft.com

Messages in this topic (0) Reply (via web post) | Start a new topic

.

You can also select the "Compile All Classes&quot; using the Project
Settings dialog.
You'll find this settings by editing the "Root" of your target.

Or editing the .ecf by using : all_classes="true"

<root class=&quot;TEST"; feature=&quot;make&quot; all_classes="true" />

Now it is up to you to use this, since it will compile all the classes ..

Hope this helps
--Jocelyn

On 3/22/2007 23:33 PM, Eric Bezault wrote:
&gt; rfo%40amalasoft.com">rfoamalasoft.com wrote:
&gt;
>>; Ah yes. When a library has been precompiled this is clearly the best option. When dealing with other repositories though, this is not an option. Unless the class you seek has been compiled, it cannot reveal its relationships (that psychic thing again). Then the grep-like method is about all there is.
>> Clearly, precompilation has a major value beyond convenience and should be the default case.
&gt;>
>
> At work I don't have this problem with whether classes are compiled
> or not. We use a Eiffel tool similar to EiffelStudio built on top
> of the Gobo Eiffel code analysis framework which doesn't suffer from
>; this problem. All classes are fully browsable, regardless of whether
> they are compiled or not.
>;
> At home I always have an EiffelStudio project with all classes
> compiled (using NONE as root class), so that I can browse the
> classes without restriction. This is explained in this LearnLet:
>
&gt; http://www.eiffel.com/developers/learning_maps/Training/Learnlets/GettingTheRightView/player.html
&gt;
> I prefer to have such an EiffelStudio project always available
> (in addition to the project I work on), rather than relying on
> grep. Had the class been called RAW_MEDIUM instead of RAW_FILE,
> I would have found it, whereas *FILE* would not. Of course this
>; assumes that the library was sufficiently well designed to get
> the inheritance graph right, which is not obvious if on the
> other hand we don't trust the way class names were chosen.
>
>

Messages in this topic (0) Reply (via web post) | Start a new topic

.

Jocelyn wrote:
&gt; You can also select the "Compile All Classes&quot; using the Project
> Settings dialog.
> You'll find this settings by editing the "Root" of your target.
>
> Or editing the .ecf by using : all_classes="true"
>
> <root class=&quot;TEST"; feature=&quot;make&quot; all_classes="true" />
&gt;
> Now it is up to you to use this, since it will compile all the classes ..

This assumes that your project contains all relevant
clusters/libraries. I prefer to have a separate project
for that. For example I won't include EiffelLex in my
project unless there is a class that I'm interested in
in that library. But this library can be included in
my separate session of EiffelStudio dedicated to
browsing classes.

But from what you described, it looks like "all_classes&quot;
has indeed the same behavior as the tool that we use at
work (which I mentioned in my previous message).

--
Eric Bezault
mailto: ericb%40gobosoft.com">ericbgobosoft.com
http://www.gobosoft.com

Messages in this topic (0) Reply (via web post) | Start a new topic

.

I wrote:
> At home I always have an EiffelStudio project with all classes
> compiled (using NONE as root class), so that I can browse the
> classes without restriction. This is explained in this LearnLet:
>
>
http://www.eiffel.com/developers/learning_maps/Training/Learnlets/GettingTheRightView/player.html

Jocelyn wrote:
&gt; You can also select the "Compile All Classes&quot; using the Project
> Settings dialog.
> You'll find this settings by editing the "Root" of your target.
>
> Or editing the .ecf by using : all_classes="true"
>
> <root class=&quot;TEST"; feature=&quot;make&quot; all_classes="true" />
&gt;
> Now it is up to you to use this, since it will compile all the classes ..

BTW, the Learnlets that EiffelSoftware put together (see the
latest EiffelWorld, or the URL below) are great. But it would
be nice if they were using a more recent version of EiffelStudio.

Learnlets portal: http://www.eiffel.com/developers/learning_maps/

--
Eric Bezault
mailto: ericb%40gobosoft.com">ericbgobosoft.com
http://www.gobosoft.com

Messages in this topic (0) Reply (via web post) | Start a new topic

.