<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/gobo-eiffel/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 23 Jan 2012 08:49:13 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/gobo-eiffel/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Documentation Needed.</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/8/</link><description>What features are supported and what aren't?

The documentation for the Gobo project doesn't reflect the the state of the system.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 23 Jan 2012 08:49:13 -0000</pubDate><guid isPermaLink="false">https://sourceforge.nete01b7204f7d1336a1a03e8a74495e48a1fea433c</guid></item><item><title>"true" or "false" are incorrect conditional</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/7/</link><description>The following instructions will report 
geant: incorrect conditional: 'true'

		&amp;lt;echo message="hello" if="true" /&amp;gt;
		&amp;lt;echo message="hello" unless="false" /&amp;gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jocelyn FIAT</dc:creator><pubDate>Tue, 03 Mar 2009 16:01:03 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7661c8efb9ad7631b967df5165d2bf35a6318910</guid></item><item><title>Naming token type</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/6/</link><description>Currently in geyacc, if one does:

%token &amp;lt;MY\_VERY\_VERY\_VERY\_VERY\_VERY\_LONG\_TYPE&amp;gt; TE\_X

in the geyacc grammar file, it generates for the tokens the attribute:

last\_my\_very\_very\_very\_very\_very\_long\_type\_value: MY\_VERY\_VERY\_VERY\_VERY\_VERY\_VERY\_LONG\_TYPE

It would be nice to have:

%token &amp;lt;keyword: MY\_VERY\_VERY\_VERY\_VERY\_VERY\_LONG\_TYPE&amp;gt; TE\_X

and it would generate for the tokens:

last\_keyword\_value: MY\_VERY\_VERY\_VERY\_VERY\_VERY\_LONG\_TYPE


It also makes sense when the type being used is a generic type, in which case geyacc generate the \_\_ between actual generic parameters.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Emmanuel Stapf</dc:creator><pubDate>Fri, 20 Feb 2009 21:16:41 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netcb0a71a3f945887972577003b4e3a14537cb2f56</guid></item><item><title>add make_from_string_general to UC_UTF8_STRING</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/5/</link><description>Message from Colin Adams in the gobo-eiffel-develop mailing list on April 21st 2008:

\[gobo-eiffel-develop\] Code to create a UC\_UTF8\_STRING from STRING\_GENERAL

Here is the functional version. It should be straight-forward to
change it to a creation procedure.

Note that it is liberal on the memory creation	of l\_bytes, to avoid
any resizing of this buffer.
		
	utf8\_string \(a\_string: STRING\_GENERAL\): UC\_UTF8\_STRING is
			\-- UTF-8 encoded version of \`a\_string'
		require
			a\_string\_not\_void: a\_string /= Void
		local
			i: INTEGER\_32
			l\_bytes: STRING			
		do
			create l\_bytes.make \(a\_string.count \* 4\)
			from
				i := 1
			until
				i &amp;gt; a\_string.count
			loop
				utf8.append\_code\_to\_utf8 \(l\_bytes, a\_string.code \(i\).as\_integer\_32\)
				i := i + 1
			end
			create Result.make\_from\_utf8 \(l\_bytes\)
		ensure
			utf8\_string\_not\_void: Result /= Void
			correct\_count: Result.count = a\_string.count
			strings\_equal: True -- can't be checked as STRING\_GENERAL and
UC\_STRING lack the facilities \(\`for\_all'\)
		end
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric Bezault</dc:creator><pubDate>Sat, 10 May 2008 11:53:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta5903da5661e65fa1afa933e609ca0c3bb35dd88</guid></item><item><title>generator indexing clause</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/4/</link><description>Make sure that getest adds an indexing clause "generator" to the classes it generates.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric Bezault</dc:creator><pubDate>Sat, 10 May 2008 11:48:39 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net1fe1d7c2c2618de2a3e862db846a35ba06c46825</guid></item><item><title>errorhandling of tasks</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/3/</link><description>Request: add the possiblility to handle/react on errors
as it is currently possible for tasks 'exec' and
'geant' to other tasks for which it makes sense as well.

Candidates are: 'copy', 'move', 'getest', ...

See also mail from 02.02.2008:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jocelyn wrote:
&amp;gt; I'd like to add :
\[...\]
&amp;gt; \* for copy, move and so on ...
&amp;gt;         accept\_errors and exit\_code\_variable  

'accept\_errors' is something I would like as well for &amp;lt;getest&amp;gt;.
For example it's not because a test fails that I don't want to
run the other tests. At first I wanted to add this functionality
to the &amp;lt;getest&amp;gt; task. Then I realized that it might be useful
for other tasks as well, so it should be a general option. So
I wanted to ask for it in the Feature Requests tracker of the
Gobo project, but then I got distracted by other things and
never took time to submit an issue to the tracker. Perhaps you
can add issues in the Feature Requests tracker, one per new
functionality you want to see added to geant. It would be
easier to follow on each of them separately I guess.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sven Ehrke</dc:creator><pubDate>Mon, 11 Feb 2008 16:15:25 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net170c648c6b3d207f656453e58a3039e6656efb2f</guid></item><item><title>Option 'supplier_precondition' in Xace</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/2/</link><description>Hello,

EiffelStudio provides a 'supplier\_precondition' option.

Is Gexace capable of generating such a 'supplier\_precondition' option?

Thanks for the support,

Best regards,

Paul G. Crismer</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric Bezault</dc:creator><pubDate>Sun, 13 Jan 2008 22:39:17 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net19e062e55027d3c81a4d032be1194100ad461e01</guid></item><item><title>STORABLE class</title><link>https://sourceforge.net/p/gobo-eiffel/feature-requests/1/</link><description>Do you plan to add STORABLE class equivalent?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 19 Aug 2002 01:55:47 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5dba40fd7a6f688f33827080962388e2f9ba1838</guid></item></channel></rss>