This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Five Lines of Code and have Christian Clausen on-line!
See this thread for details.
Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

A new file or not

 
Ranch Hand
Posts: 161
Firefox Browser Java Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Yall,
I have a question about the style of programming.

If I have to create a small class/interface, will it be a good idea to create a new file or just write it along the file which will use it. I always thought it will be best to always separate classes and interface in each java file.

I am interested in others opinion or experience.

Holler,
Garry
 
Bartender
Posts: 1847
14
Eclipse IDE Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When you say interface... you don't mean a real interface (as in something a class implements), right?

You mean like a user interface?

I like this format myself

Main method starts the user interface:



and then create a HAS a relationship so the UI can interact with the algorithms you need.

Dunno if it's "javaranch correct" but it's what I've done and it seems pretty clean.
 
Gary Ba
Ranch Hand
Posts: 161
Firefox Browser Java Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here is what I mean....



My question is....
Is it in good practice to separate the OtherClass and ClassName in two files or one file?
 
Janeice DelVecchio
Bartender
Posts: 1847
14
Eclipse IDE Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can do either, but I make 2 separate files incase something else ever implements the same thing.

Again.... not sure of the JR right way.....
 
Sheriff
Posts: 9099
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think it's usually best to maintain 2 files unless one is an inner class.
 
    Bookmark Topic Watch Topic
  • New Topic