|
From: Eric B. <er...@go...> - 2001-08-12 11:50:19
|
Christian Couder wrote: > > Ok, so I agree with you that put_line features are a good thing, but I > don't think they solve the whole problem. > > For example if you want to set a multi-line message in a message box, > you can use one of the following : > > 1) > > msg_box.set_msg(error_header + eol + error_msg + eol + help_msg) > > 2) > > msg_box.set_msg(error_header + "%N" + error_msg + "%N" + help_msg) > > 3) > > my_msg.append_line(error_header) > my_msg.append_line(error_msg) > my_msg.append_string(help_msg) > msg_box.set_msg(my_msg) > > >From this example you can see that 1) is both very short and likely to > be portable, while 2) is not likely to be portable and 3) is not short. But I would rather use 3) anyway: I don't want to have to create zillion objects just to display a message. And apparently your 'eol' is part of ANY, so I think that this should rather be discussed in NICE and be adopted by the Eiffel compilers since they have better ways to handle platform-dependent functionalities than library writers. -- Eric Bezault mailto:er...@go... http://www.gobosoft.com |