Right...
We are using this file Prompt.class in class for console inputs with
validations of input types. I guess I'll stick with the Scanner for
now! We have no way of finding the sourcecode for this class since he
got it from some guy on a university. :S
Thanks
> We are using this file Prompt.class in class for console inputs with
> validations of input types. I guess I'll stick with the Scanner for
> now! We have no way of finding the sourcecode for this class since he
> got it from some guy on a university. :S
I would always prefer an official Java API class over
some code from the net.
Especially if the code from the net comes without
packages, because that does not imply good quality.
Arne
PS: If you have sufficient license rights to the code you
could decompile it, add package and recompile.
nivanson - 01 Oct 2006 17:03 GMT
> > We are using this file Prompt.class in class for console inputs with
> > validations of input types. I guess I'll stick with the Scanner for
[quoted text clipped - 11 lines]
> PS: If you have sufficient license rights to the code you
> could decompile it, add package and recompile.
It isn't good quality. -..- It even mixes swedish and english naming in
it's functions. Though it has some obvious advantages over the Scanner
that we also got introduced to. Sooner in our course we will write our
own input libraries I think... Or start using Swing or SWT (or qt4 if
my suggestion passes).
Thanks for answering my question! I'll try the decompiler for fun ^^