Can we use EiffelBuild for a large project or should we limit its use for prototyping?

EiffelBuild is a graphical ISE GUI tool for Eiffel.

I tried, and I find it very convenient, but I'm a little worried about using such a tool for a large project. Using a GUI build tool can be restrictive.

Since Eiffel inheritance simplifies component creation, in the long run it may be better to use our own specialized versions of graphical objects that will use standard ones.

Do you know the limitations of EiffelBuild that justify its use for large projects.

+3
source share
2 answers

I would limit the use of EiffelBuild to a prototype. This is a good tool, but it will ultimately be more difficult to manage EiffelBuild projects (and this is true for most designers):

  • New versions of estudio are released every 6 months, which makes it necessary to keep your EiffelBuild projects still, as expected, from one version to another, and every time you have to deal with migrations. Now all your Eiffel code will be subject to the same challenges, but with projects in EiffelBuild you will have to deal with both changes in AND EiffelBuild (and sometimes at the same time ...)
  • N + 1 N , EiffelBuild , .
  • EiffelBuild
  • EiffelBuild, (, ...), EiffelBuild
  • , EiffelBuild, , .

, .

+3

, , , . GUI .

""? ?

, , , , . , , , . , .

Eiffel , , .

? , , perpetuam. , , , . , .

, , . , .

:

, 90- , - . ++ , , Java Sun, # . , .

"- Meyers". DbC, - - . , , .

, , . # , Windows; Java, Microsoft.

SO Eiffel. , -. , , . , Beta , VHS, , . . , .

2:

- , .

" " , , Eiffel , . . , .

, . , , . , , Eiffel ?

, , , , Eiffel, : , , .. , - .

+1
source

Source: https://habr.com/ru/post/1717521/


All Articles