Forum

by Jocelyn-Fiat (modified: 2018 Sep 05)

:: Welcome :: Forum

Eiffel related groups and forums:

Check the latest messages:

  • Aug 18
    RE: [eiffel-users] Re: Returning to Eiffel
    No. -- BM From: eiffel...@googlegroups.com [mailto:eiffel...@googlegroups.com] On Behalf Of Bernd Schoeller Sent: Sunday, 18 August, 2019 01:43 To: eiffel...@googlegroups.com Subject: Re: [eiffel-users] Re: Returning to Eiffel Hello ECMA people ;-) Just a short question concerning
  • Aug 18
    Re: [eiffel-users] Re: Returning to Eiffel
    I don't think this has been discussed. But it does not work anyway because we also want to be able to call this kind of features in regular object calls: c := {COLOR}.red c := my_color.red So, to follow your suggestion, it should have been: Current = Void or Current /= Void
  • Aug 18
    Re: [eiffel-users] Re: Returning to Eiffel
    That's what I had setup too, though with a snafu: the program name is case sensitive in the XML file so at first StepThree did not match stepthree.exe. But still don't see the other presentation I hope to get. I wonder if there is a hidden switch in the WEL package that does not get properly set
  • Aug 17
    Re: [eiffel-users] Re: Returning to Eiffel
    Hello ECMA people ;-) Just a short question concerning this: Had it been discussed to use 'Current = Void' instead of 'class' ? Why was this dismissed? Regards, Bernd On 29/07/2019 06:17, Bertrand Meyer wrote: This is a recent addition. See https://dev.eiffel.com/EiffelStudio_18.01_Releases.
  • Aug 17
    Re: [eiffel-users] Re: Returning to Eiffel
    YOUR_EXE_NAME
  • Aug 17
    Re: [eiffel-users] Re: Returning to Eiffel
    > Windows didn't seem to pick up the manifest, although tailored according > to > https://docs.microsoft.com/en-us/windows/win32/controls/cookbook-overview , > and dropped side-by-side to the exe, both in workbench mode and in a > finalized version. Still looking for an answer.
  • Aug 16
    Re: [eiffel-users] Re: Returning to Eiffel
    You need the Windows manifest file in the same folder as the EXE. Stupid, I know, but there it is.
  • Aug 16
    Re: Returning to Eiffel
    I created a small window layout in EiffelBuild and generate / compile it. The presentation looks vey different in the run time version than in the develpment presentation. EIffelBuild shows: [image: Main window in EiffelBuild.png] Runtime started out of EiffelStudio (native Windows, not
  • Aug 15
    Re: Newbie question on code reuse - using a previous project
    Thanks for the input, guys. In my case I frequently have several 'experimental' applications, and rarely have a finished 'primary' from which to base the others. I tend to pick the last variant that is closest to my next idea and work from there. I do also have classes that rarely change, and
  • Aug 13
    Re: Newbie question on code reuse - using a previous project
    Management library. Think of it as a library for creating "Swiss-army knife applications". Visit the link for details. You inherit EL_MULTI_APPLICATION_ROOT in your root class. An example of it's use in the root class of project toolkit.ecf: APPLICATION_ROOT Note: currently Eiffel-loop only
  • Aug 13
    Re: Returning to Eiffel
    I guess I have found the relevant discussion to my question at Void-safety: Background, definition, and tools on Eiffel.org.
  • Aug 13
    Re: [eiffel-users] Re: Newbie question on code reuse - using a previous project
    Together with good project organization and the appropriate culling out of classes into small libraries—one also has the notion of project "targets". I have a tool that I built for myself that creates a new project with a minimum of two targets—a primary project target and a test target. What
  • Aug 13
    RE: [eiffel-users] Re: Newbie question on code reuse - using a previous project
    Happens all the time. Well, it happens. First, you should organize your originating project into what is, and isn't reusable. This is always a good exercise and leads to a more robust (read: compulsive) class-oriented/reusable-component mindset, from which you will not likely ever recover. The
  • Aug 13
    Re: Newbie question on code reuse - using a previous project
    Slightly OT (a regular occurrence with me), I often find myself wanting to make a variant of a project, and it would be handy if there was a way to 'copy & rename' a project in a couple of clicks (assuming I haven't missed this option somewhere). At the moment I do this by creating a new project
  • Aug 10
    Re: Newbie question on code reuse - using a previous project
    Hi Hank, As the others have responded, there is a cluster option and a library option. Myself—I tend to the library option, creating many small specialized libraries. I do this in a step-wise fashion—creating a cluster within my project to start and then migrating that cluster out into a
  • Aug 10
    Re: [eiffel-users] Re: Returning to Eiffel
    Is this not why we have SCOOP? On Friday, August 9, 2019 at 2:33:47 PM UTC-4, colinpauladams wrote: > > Probably first_window is an attribute of the class. Then there is the > possibility of multi-threading to take into account (first_window might > become detached on another thread). > > On
  • Aug 10
    Configuration/version management
    The topic of built-in support for configuration management within EiffelStudio comes up regularly. So far the internal view has been that each organization has its own approach to configuration management and that we don’t want to be imposing a particular method or tool. That point was made long
  • Aug 10
    A question about SCOOP and C
    I have been looking through the SCOOP documentation and I couldn't find anything as it relates to making asynchronous calls to C routines via the external keyword. Is it possible? What is the relation of SCOOP to the C world?
  • Aug 09
    Re: [eiffel-users] Re: Returning to Eiffel
    Probably first_window is an attribute of the class. Then there is the possibility of multi-threading to take into account (first_window might become detached on another thread). On Fri, 9 Aug 2019 at 19:20, Richard wrote: > Some words of wisdom, please > > From a
  • Aug 09
    Re: Returning to Eiffel
    Some words of wisdom, please From a VisualEiffel example the main class below with a snippet of interest highlighted in blue. I attempt to replace it by the snippet highlighted in brown. The compiler is cautious on void saftey and marks my code with VUTA(2) (see below). My question: What is
  • Aug 09
    Re: [eiffel-users] Re: Returning to Eiffel
    Hi, Thanks for all the valuable feedback. We'll try to address each of them, especially for the preferences and shortcuts. About eiffel.org, you can contact the Eiffel.org webmaster team using https://www.eiffel.org/contact -- Jocelyn On Fri, Aug 9, 2019 at 1:54 AM Richard
  • Aug 08
    Re: Returning to Eiffel
    Eiffel dot Org - the Community information portal While several sections have a comment function this is not the case for erverything. Question: how do I contact the web host for pointing out discrepancies? Like in the Resources division, the Libraries page at https://www.eiffel.org/resources/l
  • Jul 30
    Re: Returning to Eiffel
    Me Culpa! I should not be posting late night to a mailing list, cannot silently fix like on a forum ;) i Of course my "minimalistic" version has gone too minimalistic by dropping the item that implies the difference of the objects. Different names for the same stuff makes no different objects ;(
  • Jul 30
    Re: Understanding the idea behind explicitly specifying Generic parameters
    Thx Larry, good point! the only thing that annoys me on that case is the refactoring in case I'd like to change the generic constraint of that class which happened to me (and think many of us) anytimes, in that case it becomes more complicated. But yes, using a `like ` reference is helping many
  • Jul 30
    Re: Returning to Eiffel
    For the record and free to steal the suggestion. Based on the prior discussion of the removed unique and with the code snippet supplied by Alexander Kogtenkov as suggested replacement I tinkered and came up with following minimalistic approach. note description: "Minimalistic enumeration class
  • See more ...