Re: input/output exceptions

[Robert Dewar <robert_dewar@my-deja.com>]

In article <8v6lfe$rc7$07$1@news.t-online.com>,
  Amal Kurian <kurian.amal@t-online.de> wrote:
> While Robert Dewar pointed out, that 2.54 contains 2 and
> "junk" he should  also have stated that since 2.54 is the last
> value to be read in, Ada  ignores the junk and the program
> finishes while it couldn't ignore it if
> there is still something to be read in. ]


I find the above formulation confusing, it implies there is
something special about Ada here.

In fact it's quite simple. If you have junk in the input,
and you do not read the junk, the program will not notice
there is junk.

I would expect that to be true of any language with a
reasonably straightforward view of sequential input.

The only thing that is special about Ada, and hence really
the only point that needs special comment is that if
you write 2.54 and read an integer, then only the 2 is
read.

I think it is very important for people to have the skills
to figure out the obvious consequences of rules like this.
Yes, I deliberately did not spell out those obvious
consequences, because I think it is a good idea for people
to think their way through things.

If you make the effort to think your way to the right
conclusion, given the basic axioms, and learn how to do
this, then you learn a really valuable lesson, and perhaps
you will be able to solve your next problem without asking
CLA. It is interesting to note that the original questioner
was not the one complaining about the lack of a full answer :-)


Sent via Deja.com http://www.deja.com/
Before you buy.