I get your point (Python, instead of Make). Good point.

Hello - Sorry, guys, I don't mean to be a provocateur or anything, but, just looking at the Smalltalk community, as you probably know, there's been a sort of rebirth with Pharo Smalltlak, and one of the thing they did was free all the out-of-print books for downloading. Have you seen that? From

-- Hank PS: Lots of good info out there. Why are we not blogging / posting / advocating ?

Thanks, Eric. Is there a way of following this report up? That is, another than inspection from time to time? Em terça-feira, 16 de julho de 2019 16:35:47 UTC-3, Eric Bezault escreveu: > > (...) > > There is already a bug report for that: > > https://support.eiffel.com/report_detail/19535 > > >

There is already a bug report for that: https://support.eiffel.com/report_detail/19535 -- Eric Bezault mailto:er...@gobosoft.com http://www.gobosoft.com

I have aliased some features with "decorated" operators, like ∃², ∄², ∀², ∃ˣʸ, ∄ˣʸ and ∀ˣʸ. So far so good. I have also a feature declared filtered alias "|" (...): ... with no problem. But I can't declare the feature below filtered_xy alias "|ˣʸ" (...): ... or another like filtered_pair

Thanks for the first pointers. Just in case anyone picks up this thread in search of answers, here two links: Differences between ETL 2nd printing and Eiffel Software implementation and Differences between standard ECMA-367 and Eiffel Software implementation

I am not recommending Python as a development language, just as something useful to learn for build scripts and has the added benefit of being popular. > I don't really care. As I said, I'm not a professional programmer, > Understood, but in any case it's not necessary to know how to program

a stable language. The TIOBE index doesn't mean much IMHO (it does for jobs). BTW, I recently checked it, looking for Eiffel. I wrote them about why do they not publish its stats, they answered that it is just statistical noise, bu it is down to 250.. .The same applies to, say, Standard ML, an

Interesting.

Hi Eiffel users, If you are using EiffelStudio 19.05 windows version (i.e the 32bit version), and if you are using McAfee solution, this one may report a threat GenericRXER-DY!A28BF822EC15 about estudio.exe and put it under quarantine (i.e delete it). See https://www.virustotal.com/gui/file/cf

I see. A bit of conceptual errors on my part (new to OOP).

Would you imagine writing this in Eiffel? > This is a Python script to build a code signed install package for 8 > > permutations of Windows platform, architecture and self-extracting exe > > localized language (English or German) The system ensures that you only > > have to do 1 Eiffel compile

Would you imagine writing this in Eiffel? > This is a Python script to build a code signed install package for 8 > > permutations of Windows platform, architecture and self-extracting exe > > localized language (English or German) The system ensures that you only > > have to do 1 Eiffel compile

Would you imagine writing this in Eiffel (apart from the fact that Eiffel is compiled and not interpreted)? -- Eric Bezault mailto:er...@gobosoft.com http://www.gobosoft.com

If you are using ec, you can follow the command with ">errors.txt 2>&1" without the double quotes and that will put all output to a file. Works with the Windows command line and Linux/UNIX. Or you can split standard error from standard out by using 2>other-errors.txt. On Wed, Jul 10, 2019,

EL_MODULE_ARGS from base.ecf, which gives you access to all the routines in ARGUMENTS_32 via the shared instance Args. By inheriting EL_MODULE_ARGS you are less likely to encounter name clashes as there is only one feature in the class. In addition you also get some additional convenience

Why Eiffel-Loop makes use of Python > Yes, thank you for that nice explanation! I had a "dependency hell" > experience this Sunday, as I started to manually import Eiffel Loop's > EL_PLAIN_TEXT_FILE (in order to avoid the Python-required steps - because, > well, let's just avoid non-Eiffel

I guess, you started from a new basic project where ARGUMENTS_32 was added to the root class automatically. It is there for convenience, if you would like to read command-line arguments passed to the program. There is no requirement to keep this inheritance link. Moreover, with introduction of

What about selecting all errors in the error list (with a mouse, or Ctrl+A) and then using Ctrl+C for copy? Alexander Kogtenkov Hank Lenzi : Hello Eiffel programmers -- is there a simple way to export *all* error messages to a text file, or do a copy & paste of everything?

If you want make a program (command line program) which read and write a file, you don't need inherit from EL_PLAIN_TEXT_FILE. Just add an attribute and work with it. Something like: my_file: EL_PLAIN_TEXT_FILE Germán On 8/07/19 17:27, Hank Lenzi wrote: Hi all -- In trying to use Eiffel Loop's

Hi all -- In trying to use Eiffel Loop's EL_PLAIN_TEXT_FILE, in my code, I used the following: In my APPLICATION class I have: class APPLICATION inherit ARGUMENTS_32 EL_PLAIN_TEXT_FILE Now the EiffelStudio compiler gives me this error: Error code: VMFN Error: two or more features have

experience this Sunday, as I started to manually import Eiffel Loop's EL_PLAIN_TEXT_FILE (in order to avoid the Python-required steps - because, well, let's just avoid non-Eiffel stuff if we can, right?), because, if I understand it correctly, it can work with Unicode in a better fashion than

Hello Eiffel programmers -- is there a simple way to export *all* error messages to a text file, or do a copy & paste of everything? This would be nice for source code versioning, instead of doing Control+C on each individual error message. TIA --- Hank