15 May 2013 16:26
14 May 2013 05:26
14 May 2013 05:10
10 May 2013 11:40
[Catcall Solution]Default and explicit variance
I published a new proposal for catcall resolution. The proposal is inspired of other solutions http://dev.eiffel.com/Default_and_explicit_variance If you identify english faults don't hesitate to change this. Thanks. ------------------------------------
10 May 2013 06:22
More WEL_RBBS_CONSTANTS
While trying to use a WEL_REBAR, I found that several of windows' RBBS_... constants are absent from the WEL_RBBS_CONSTANTS class, even though some of the constants are useful. Here is what's missing: Rbbs_gripperalways: INTEGER external "C [macro %"cctrl.h%"]" alias "RBBS_GRIPPERALWAYS" end Rbbs_nogripper: INTEGER external "C [macro %"cctrl.h%"]" alias "RBBS_NOGRIPPER" end Rbbs_usechevron: INTEGER external "C [macro %"cctrl.h%"]" alias "RBBS_USECHEVRON" end Rbbs_variableheight: INTEGER external "C [macro %"cctrl.h%"]" alias "RBBS_VARIABLEHEIGHT" end(Continue reading)
9 May 2013 20:54
9 May 2013 20:40
2 May 2013 20:24
Using keyword 'old'
Whilst debugging using EiffelStudio, I discovered that 'old count' is being mapped to value#1, and if there are multiples of 'old' <fields> then each gets a respective value #n assigned to it. If there are multiples of 'old' being used then one could by inference determine what is what - however is there a better way to actually map a given value #n to the actual variable (perhaps the entity could be displayed as o-count)? Any advice on techniques you use to make sense of value#n would be most welcome. thanks, Sushil. [Non-text portions of this message have been removed] ------------------------------------
2 May 2013 18:02
RE: [eiffel_software] outputting to stderr
I'm with Manu on this one, as far as the explanation goes at least. The current mechanism is no more confusing than the classic UNIX (aka "the world") one to which it's being compared and is more generally applicable. The mechanism itself should not be changed. As the issue really comes about when using 'print'. If we are worrying about confusing people, perhaps we should consider changing that, after all it has nothing to do with your printer, does it? Just seeing of you're paying attention. Back to the actual point, perhaps a convenience function or two might make people happy without causing too much of a maelstrom. For example, 'print_stdout' and 'print_stderr' could easily front end the io.* routines that do the work, just as print does today. I'd find it convenient, yet inoffensive and I suspect others might as well. It's feature creep certainly, but not a lot of it. It doesn't change the model, just dresses it up in a plaid flannel shirt and bluejeans. R ================================================== Roger F. Osmond -------- Original Message -------- Subject: RE: [eiffel_software] outputting to stderr From: "Emmanuel Stapf" <manus@...>(Continue reading)
2 May 2013 15:18
SYSTEM_STRING_FACTORY in EiffelStudio 7.2
Hi Manu, In Eiffel .NET projects, SYSTEM_STRING_FACTORY is responsible for converting back and forth between .NET String objects (which are UTF-16) and Eiffel strings (STRING_8, STRING_32, etc.). SYSTEM_STRING_FACTORY was heavily rewritten in EiffelStudio 7.2: https://svn.eiffel.com/wsvn/revision.php?repname=eiffelstudio&path=%2Ftrunk%2FSrc%2Flibrary%2Fbase%2Fise%2Fkernel%2Fdotnet%2F&rev=90063&peg=90063 https://svn.eiffel.com/wsvn/diff.php?repname=eiffelstudio&path=%2Ftrunk%2FSrc%2Flibrary%2Fbase%2Fise%2Fkernel%2Fdotnet%2Fsystem_string_factory.e&rev=90063&peg=90063 The changes seem to have been to support manipulating Unicode file paths in .NET: http://dev.eiffel.com/EiffelStudio_7.2_Releases I get the impression that the the main concern was to improve support for STRING_32 Unicode conversions, but reading the code it seems to me that it ought to work just as well for STRING_8 (i.e., UTF-8). But when I run it with our Visual Basic .NET application, Unicode characters (apart from normal ASCII) are displayed as garbage. It's the same problem that the old implementation of SYSTEM_STRING_FACTORY had. For example, this text in Arabic: قد تكون التخصيصات أكثر مناسبة للتقارير المركبة مثل حالات الميكروبيولوجيا أو الهيستوباثولوجيا ... displays like this in the .NET application: ÙØ¯ تÙÙÙ Ø§ÙØªØ®ØµÙصات Ø£ÙØ«Ø± Ù ÙØ§Ø³Ø¨Ø© ÙÙØªÙØ§Ø±ÙØ± اÙÙ Ø±ÙØ¨Ø© Ù Ø«Ù ØØ§Ùات اÙÙ ÙÙØ±ÙبÙÙÙÙØ¬Ùا أ٠اÙÙÙØ³ØªÙباثÙÙÙØ¬Ùا(Continue reading)
1 May 2013 17:47
outputting to stderr
most command line Eiffel programs send feedback to the console with
either io.put_string () or print (). I need to control this properly to
be output => stdout and error output to std_err. It appears that the
only way to do this is to use the STD_FILES modal set_error_default and
set_output_default calls.
That means if you have some code that wants to do (logical pseudo-code):
...
stdout.put_string ("xxxxx")
...
stderr.put_string ("err err err")
...
stdout.put_string ("xxxxx")
you actually have to do:
...
io.put_string ("xxxx")
...
io.set_error _default
io.put_string ("err err err")
io.set_output_default
...
io.put_string ("xxxxx")
and you only get away with that if you trust that no developer forgot to
switch the default output back to standard out after reporting an error.
(Continue reading)
RSS Feed