https://sourceforge.net/p/gobo-eiffel/feature-requests/2012-01-23T08:49:13ZRecent changes to feature-requests2012-01-23T08:49:13Z2012-01-23T08:49:13ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.nete01b7204f7d1336a1a03e8a74495e48a1fea433c

What features are supported and what aren't? The documentation for the Gobo project doesn't reflect the the state of the system.

2009-03-03T16:01:03Z2009-03-03T16:01:03ZJocelyn FIAThttps://sourceforge.net/u/jfiat/https://sourceforge.net7661c8efb9ad7631b967df5165d2bf35a6318910

The following instructions will report geant: incorrect conditional: 'true' <echo message="hello" if="true" /> <echo message="hello" unless="false" />

2009-02-20T21:16:41Z2009-02-20T21:16:41ZEmmanuel Stapfhttps://sourceforge.net/u/userid-1044918/https://sourceforge.netcb0a71a3f945887972577003b4e3a14537cb2f56

Currently in geyacc, if one does: %token <MY\_VERY\_VERY\_VERY\_VERY\_VERY\_LONG\_TYPE> 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 <keyword: MY\_VERY\_VERY\_VERY\_VERY\_VERY\_LONG\_TYPE> 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.

2008-05-10T11:53:35Z2008-05-10T11:53:35ZEric Bezaulthttps://sourceforge.net/u/ericb/https://sourceforge.neta5903da5661e65fa1afa933e609ca0c3bb35dd88

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 > 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

2008-05-10T11:48:39Z2008-05-10T11:48:39ZEric Bezaulthttps://sourceforge.net/u/ericb/https://sourceforge.net1fe1d7c2c2618de2a3e862db846a35ba06c46825

Make sure that getest adds an indexing clause "generator" to the classes it generates.

2008-02-11T16:15:25Z2008-02-11T16:15:25ZSven Ehrkehttps://sourceforge.net/u/svene/https://sourceforge.net170c648c6b3d207f656453e58a3039e6656efb2f

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: > I'd like to add : \[...\] > \* for copy, move and so on ... > accept\_errors and exit\_code\_variable 'accept\_errors' is something I would like as well for <getest>. 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 <getest> 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. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2008-01-13T22:39:17Z2008-01-13T22:39:17ZEric Bezaulthttps://sourceforge.net/u/ericb/https://sourceforge.net19e062e55027d3c81a4d032be1194100ad461e01

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

2002-08-19T01:55:47Z2002-08-19T01:55:47ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net5dba40fd7a6f688f33827080962388e2f9ba1838

Do you plan to add STORABLE class equivalent?