Well—I just answered my own question pretty easily! BASE_PROCESS and BASE_PROCESS_FACTORY.

I would suggest using base_process library instead. It works with and without SCOOP. The main difference from the "regular" process library is lack of agent-based input-output redirection. If you do not use such functionality, it would be a good replacement. Alexander Kogtenkov Larry Rix

Okay—at first glance, Alex's solution of dropping the thread library and using base_process appears to have worked. My library is now using SCOOP instead of Thread. What I still do not understand is the different between "support" and "use" in the tag in the ECF. Thoughts?

Thanks for the suggestion, Alex Do you know what I can use to replace PROCESS and PROCESS_FACTORY in base_process? [image: image.png]

Larry Rix : What I still do not understand is the different between "support" and "use" in the tag in the ECF. In general, it's better to use EiffelStudio to edit project settings. Doing it by hand may lead to unexpected results, because there

I have a library which uses the Process + Thread libraries. The concurrency setting is set to "thread" in this library. Switching it to "scoop" causes a configuration error when attempting to compile. For example: I change the concurrency setting from "

I have this piece of code below and I am getting errors or my logic probably isn't correct. It would be great if someone can help me fix the code. Thanks :-)

concatenate (a: ARRAY [G]; b: ARRAY [G]): ARRAY [G]
    require
        constraints_on_lower_indices:
            -- Do not modify this precondition.
            a.lower = 1 and b.lower = 1
    do
        create Result.make_empty
        size1 := a.capacity
        size2 := b.capacity
        from  i := 0
        until i <= size1 - 1
        loop
            c [i] := a [i]
        end
        from  i := 0
        until i <= size2 - 1
        loop
            c [i + size1] := b [i]
        end
        -- TO DO
    ensure
        constraint_on_lower_index:
            -- Do not modify this postcondition.
            Result.lower = 1
        correct_size:
            Result.capacity = size1 + size2
            -- TO DO: replace False with your postcondition.
        --  correct_contents:
            --  across
            --      Result as elements
            --  loop
            --      Io.put_string (elements.item)
            --      Io.new_line
            --  end
            -- TO DO: replace False with your postcondition.
            -- The final result must be the concatenation of
            -- the two argument arrays.
            -- Hint: You may use `across' as a universal quantifier.
    end

Oh, sorry. I don't recall getting such permissions. No worries.

Thanks for your reminder. I checked and I have access and will try to contribute when I see something that needs update. On Mon, 21 Jan 2019 at 11:53, Jocelyn Fiat wrote: > Hi Larry, > > I confirm that you already have edit permissions on eiffel.org > documentation. > I sent a

Hi Larry, I confirm that you already have edit permissions on eiffel.org documentation. I sent a message .. months, or years ago to notify you and a few others about that. If ever you need any help to edit documentation, or find issue, please let me know. Also, as eiffel.org is the Eiffel

A possibly useful recent thread where Manu addresses concurrency: https://groups.google.com/forum/#!searchin/eiffel-users/concurrency%7Csort:date/eiffel-users/KXl-bpoUXNE/a67UUsyMDwAJ and one where Bertrand and Alexander both weighed in : https://groups.google.com/forum/#!searchin/eiffel-users/Voi

Thanks for the feedback! On Sun, Jan 20, 2019 at 8:01 PM Eric Bezault wrote: > On 20/01/2019 23:18, Larry Rix wrote: > > From the point of view of GitHub, here are the changes you will make if > > you perform the steps outlined by Bertrand in the linked paper. > > This

This view is excellent. It shows how simple the modifications are. It should probably be added as a summary at the end of the paper. -- Eric Bezault mailto:er...@gobosoft.com http://www.gobosoft.com

So—I want to switch to using SCOOP. My ereport project uses my framework library. The framework library was using Thread concurrency. The ereport library project was the same. The following manual hack of the ECF does not ultimately work. - Changed Concurrency: - From:

OpenBSD versions? estudio fails to run with loader errors in OpenBSD 6.4. Hi Rick, Some time ago, I tried getting it to run on OpenBSD a few years ago. My experiences are described in https://www.eiffel.org/blog/schoelle/porting_eiffelstudio_to_openbsd_again Now, the main blocker at that

From the point of view of GitHub, here are the changes you will make if you perform the steps outlined by Bertrand in the linked paper. CLIENT: [image: image.png] DOWNLOADER: [image: image.png] PARAMETERS: [image: image.png] VIEWER: [image: image.png]

You are quite welcome! Larry Rix Moonshot Software Rocket science for everyone! Savannah, GA 770-295-9729 On Sun, Jan 20, 2019 at 5:07 PM Bertrand Meyer wrote: > Dear Larry, > > > > Thanks a lot! > > > > For lack of time in the coming days I think I will leave

Dear Larry, Thanks a lot! For lack of time in the coming days I think I will leave things as they are for the moment. (If you want to edit the eiffel.org page to mention the github variant please go ahead.) I would gladly let you update the text but you would need to have FrameMaker.

I do not have access to edit Eiffel.org, so I will leave that to others. :-) Larry Rix Moonshot Software Rocket science for everyone! Savannah, GA 770-295-9729 On Sun, Jan 20, 2019 at 5:07 PM Bertrand Meyer wrote: > Dear Larry, > > > > Thanks a lot! > > > > For

I have created a version of the project(s) as a single ECF file and placed it in GitHub here. 1. When you open the ECF, select the target you want (Concurrent, Sequential, or Scratchpad). You may open each target in its own independent instance of Eiffel Studio. 2. Take note of the class Note

On Tuesday, September 8, 2015 at 2:00:09 PM UTC-7, 'Emmanuel Stapf' ma...@eiffel.com [eiffel_software] wrote: > We are still compiling against OpenBSD 4.8 for higher backward compatibility. If really EiffelStudio does not work under 5.5, I would recommend recompiling it yourself. > > Although

The video can be found here. The highlights are: 1. Delete or rename your corrupted ECF file. I recommend renaming and moving to another location on your file system. You can still use it as a reference, but it is away from where it will be confusing. 2. Open Eiffel Studio to where

SITUATION: You have an existing ECF. Something has gone horribly wrong. Your project will not compile and the errors stem from how you have your ECF configured. There are (perhaps) several solutions: 1. Learn—try to figure out what is wrong and fix it. However, this might be more complex than

Hi Gerrit, The way I have learned to configure the ECF targets is not standard. If I were in your shoes, I would put my attention on how Auto Test sets itself up by default in your project and just go with that. What my learned configuration is really about is segregating the testing bits from

Hi Larry, this is what I am used to do in a Maven/JUnit4 or .NET core/NUnit Project: separate the Tests from the production or library. Everything else would be a pain! G. Gesendet von Mail für Windows 10 Von: Larry Rix Gesendet: Sonntag, 20. Januar 2019 14:35 An: Gerrit Leder Cc: