> On Wed, 26 Aug 1998 11:33:42 -0300 (ADT), Kenny Freeman wrote:
>
> >
> >> I personally am rather against most import statements as they can
> >> only help to confuse the issue of what you are looking at. Even worse
> >> is import of a whole package - since then you do not even see in the
> >>
Hello,
You said you have an editor "that makes life easier". What's that for?
Thanks for your answer.
-jec
> -Original Message-
> From: Michael Sinz [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, August 26, 1998 4:50 PM
> To: Kenny Freeman
> Cc: [EMAIL
On Wed, 26 Aug 1998 12:02:55 -0300 (ADT), Kenny Freeman wrote:
>I see your point now. I agree with you when you say doing this is a bad
>thing:
> import foo.bar.*;
> import foo2.bar2.*;
>This does cause problems and is not nec. a good thing to do - but I was
>generally thinking allong
> On Wed, 26 Aug 1998 11:33:42 -0300 (ADT), Kenny Freeman wrote:
>
> >
> >> I personally am rather against most import statements as they can
> >> only help to confuse the issue of what you are looking at. Even worse
> >> is import of a whole package - since then you do not even see in the
> >>
On Wed, 26 Aug 1998 11:33:42 -0300 (ADT), Kenny Freeman wrote:
>
>> I personally am rather against most import statements as they can
>> only help to confuse the issue of what you are looking at. Even worse
>> is import of a whole package - since then you do not even see in the
>> code all of t
> I personally am rather against most import statements as they can
> only help to confuse the issue of what you are looking at. Even worse
> is import of a whole package - since then you do not even see in the
> code all of the possible class names that just got defined... However,
> if used
On Wed, 26 Aug 1998 15:54:36 +0200, Maarten van Leunen wrote:
>Howdie,
>
>Anyone know how these darned packages work? Or where a good guide is
>available concerning packages?
>
>I can't seem to find anything about it in the nice Sun Java Tutorial.
Well, it is covered in "The Java Programming Lan
