eiffelroom - help - Comments

Path URI

nenieorg — Fri, 16 May 2008 08:01:34 -0700

Yes path URI sounds so much better than the name value mess, and is not exclusive with defaulting of various types, with say a magic word as first component:

eiffel:///byclass/STRING/is_equal eiffel:///bycluster/foo/STRING/is_equal

etc

Though I am not aware of

ted_eiffel — Wed, 14 May 2008 07:28:24 -0700

Though I am not aware of what kind of software processes the URI and how it would be useful picking up name/value pairs, it is would always be better to follow standard. Using eiffel:///? is OK for me, except that it looks uglier. Actually the .ecf is not needed for EIS incoming mechanism. Only optional system/system UUID is needed for locating project.

Perhaps a path

colin-adams — Tue, 13 May 2008 07:35:48 -0700

You would need eiffel:///?... if you expected generic URI processing software to pick up the name/value pairs.

or alternatively abandon the query parameters approach, and have a structured path (something like /system/target/cluster/class/feature). But that would make it hard to default the system and target.

I can't see how this is supposed to work anyway. Surely you need an ecf file? In which case the obvious syntax is:

eiffel:///path/to/my.ecf?class=my_class&feature=my_feature

and the authority field is then available for a future extension for non-local access.

Colin Adams

Indeed. I think eiffel:///

ted_eiffel — Tue, 13 May 2008 05:04:22 -0700

Indeed. I think eiffel:/// would be nicer.

Invalid URIs

colin-adams — Tue, 13 May 2008 03:18:33 -0700

The syntax of the eiffel: URIs is invalid.

That is, the presence of the // indicates that what follows is an authority segment:

According to RFC 3986, this is terminated by the first /, ? or # character.

None of those is present, so the remainder of the URI needs to match the authority production syntax. As there is no @ or : present, this in turn means matching the syntax for host. Clearly it does not.

I suggest that you appear to be parameter/value pairs, and that therefore this remainder should actually be part of the query segment.

Accordingly, change eiffel:// into eiffel://? in order to conform to URI syntax.

I assume that by protocol link you actually meant URI scheme.

Colin Adams

Typo?

colin-adams — Thu, 19 Apr 2007 22:49:43 -0700

Hello Jasmine,

Firstly, it would be easier to read your code if you included it within eiffel XML tags (see MediaWiki syntax when posting).

I can see a few problems with your code.

Firstly, it should be io.last_string (you omitted the io.). Secondly, I think you need to call io.last_string.twin, which will copy the last string. The problem is that io.last_string is re-used, so all the entries in your array point to the same object.

Thirdly, since you know the size of the array, it would be better to size it correctly, and use put, not force.

Also, avoid loops when you can (not always possible). Agents are better.

So something like this:

feature -- Test

test is

  -- Test reading multiple words from standard input

local

 my_array: ARRAY [STRING]

 i: INTEGER

do

 create my_array.make (1, 10)

 from

  i := 1

 until

  i > 10

 loop

  io.read_word

  my_array.put (io.last_string.twin, i)

  i := i + 1

 end

 my_array.do_all (agent print_line)

end

print_line (a_string: STRING) is

  -- Print `a_string' on standard output followed by a new line.

require

 a_string_not_void: a_string /= Void

do

 print (a_string + "%N")

end

Colin Adams