Submitted by Colin LeMahieu on Wed, 11/18/2009 - 20:49.
These tests test the allocation performance of 3 passback variable options and the subsequent access time when retrieving the value back from the calling function.
The difficulty in a general solution arises with void safety.
Submitted by Creative Bachkhoa on Sat, 10/31/2009 - 04:29.
I've tested the system by an example of exception handling in Eiffel
<eiffel>
feature {NONE} -- Initialization
i:INTEGER
x:REAL
y:ARRAY[REAL]
make
-- Run application.
do
create y.make(1,2)
io.put_string ("The item at position: ")
io.read_integer
i:=io.last_integer
find
io.put_string (" is: ")
io.put_real (x)
io.put_string ("%NReturn to make i
Submitted by Colin LeMahieu on Tue, 07/14/2009 - 21:32.
This is a short template of what one can do when dealing with the perfect storm of complication using attached variables. This issue can arise when you need to attempt to release a resource, e.g.
Submitted by Jocelyn Fiat on Mon, 09/22/2008 - 17:01.
This is a quite basic but essential operation: Launch a command, and get its output in a string.
There are various solutions.
One is to redirect the output to a temporary file, and then read its content. But this is not convenient, since it require disk access, and you can not always hide the process.
Submitted by Francesco Ferreri on Mon, 08/25/2008 - 16:52.
After several months programming with Ruby scripting language, and related libraries, I got quite used to the intensive use of iterators and blocks (closures) that give Ruby programs a particular coding flavour.
