[program-java] Re: Beginning Java Ramblings

  • From: "Corbett, James" <James.Corbett@xxxxxxxxxxxxx>
  • To: "'program-java@xxxxxxxxxxxxx'" <program-java@xxxxxxxxxxxxx>
  • Date: Wed, 2 Feb 2011 13:35:41 -0500

Roger and Jim:

To muddy the water further, you can have a nested class with in a class that by 
its self is private.

Jim


James M. Corbett

Programmer / Analyst |
Canada Revenue Agency | Agence du revenue du Canada
875 Heron Rd.
Ottawa, On.
K1A0L5

James.Corbett@xxxxxxxxxxxxx
Telephone | Téléphone: (613) 941-1338
Facsimile | Télécopieur: (613) 941-2261

Government of Canada | Gouvernement du Canada

E = MC²

-----Original Message-----
From: program-java-bounce@xxxxxxxxxxxxx 
[mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Roger Woolgrove
Sent: February 2, 2011 13:11
To: program-java@xxxxxxxxxxxxx
Subject: [program-java] Re: Beginning Java Ramblings

Hi Jim and Jim,

Agree with Jim on this one.  You may have more than 1 public class.

I am presently studying OOP with Java with the Open University and am 
apparently the first blind student on this course.

Don't worry about how many classes you can have, each class acts independently 
and may be used by other classes provided they are not private as opposed to 
public.

I am presently working on a project for a committee and there are 2 interfaces 
for the users.  One is reserved for all members and the other is for the 
committee members only.

HTH

Roger


----- Original Message -----
From: "Corbett, James" <James.Corbett@xxxxxxxxxxxxx>
To: <program-java@xxxxxxxxxxxxx>
Sent: Wednesday, February 02, 2011 3:57 PM
Subject: [program-java] Re: Beginning Java Ramblings


Jim:

You can have many so called public interfaces to a STRUTS / Java application
and none of them have a Main but before you get confused let's just say that
for a desktop application at this point there is a single public interface.

Jim


James M. Corbett

Programmer / Analyst |
Canada Revenue Agency | Agence du revenue du Canada
875 Heron Rd.
Ottawa, On.
K1A0L5

James.Corbett@xxxxxxxxxxxxx
Telephone | Téléphone: (613) 941-1338
Facsimile | Télécopieur: (613) 941-2261

Government of Canada | Gouvernement du Canada

E = MC²

-----Original Message-----
From: program-java-bounce@xxxxxxxxxxxxx
[mailto:program-java-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James
Sent: February 2, 2011 10:31
To: program-java@xxxxxxxxxxxxx
Subject: [program-java] Beginning Java Ramblings

Hi,



Please keep in mind that all I have studied so far is the first programming
chapter of Java For Programmers, by Deitel. We don't get to anything but
public classes until Chapter 8. Is this anywhere in the ballpark?



Here's an analogy that seems to work for me. If you've ever worked with sub
programs in Cobol, a public class is  something like a Cobol subprogram. A
Cobol subprogram is a program all by itself, with its own working storage
and routines. You can execute it from another Cobol program. The main Cobol
program can see all of the variables and routines in the subprogram. I'm
pretty sure that like Java, Cobol forces you to have one program per file.
In Java, you have to have one public class per file.



At this point, we haven't talked about any other methods besides main, so
that's all we know about methods. We don't know about private or anything
else right now.







Jim Homme,

Usability Services,

Phone: 412-544-1810. Skype: jim.homme

Internal recipients,  Read my accessibility blog
<http://mysites.highmark.com/personal/lidikki/Blog/default.aspx> . Discuss
accessibility here
<http://collaborate.highmark.com/COP/technical/accessibility/default.aspx> .
Accessibility Wiki: Breaking news and accessibility advice
<http://collaborate.highmark.com/COP/technical/accessibility/Accessibility%20Wiki/Forms/AllPages.aspx>




________________________________

This e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed. If
you have received this e-mail in error, please notify the sender immediately
and then delete it. If you are not the intended recipient, you must not
keep, use, disclose, copy or distribute this e-mail without the author's
prior permission. The views expressed in this e-mail message do not
necessarily represent the views of Highmark Inc., its subsidiaries, or
affiliates.

Other related posts:

  1. Home
  2. program-java
  3. Archive
  4. 02-2011