Archive:Java/Programming tips - Revision history

wikademia>Wikademia: moved Java/Programming tips to Archive:Java/Programming tips

2009-06-20T19:14:43Z

moved Java/Programming tips to Archive:Java/Programming tips

← Older revision		Revision as of 19:14, 20 June 2009
(No difference)

wikademia>Wikademia: moved Java programming tips to Java/Programming tips

2009-06-12T16:19:00Z

moved Java programming tips to Java/Programming tips

← Older revision		Revision as of 16:19, 12 June 2009
(No difference)

wikademia>Wikademia: Text replace - '[[Topic:' to '[['

2009-06-08T03:56:05Z

Text replace - '[[Topic:' to '[['

← Older revision		Revision as of 03:56, 8 June 2009
Line 104:		Line 104:


	{{1lvlnav\|[[~~Topic:~~Java\|Java]]\|[[Important Java Classes]]\|[[Java/Fundamental Exercises\|Fundamental Exercises]]}}		{{1lvlnav\|[[Java\|Java]]\|[[Important Java Classes]]\|[[Java/Fundamental Exercises\|Fundamental Exercises]]}}
	[[Category:Java]]		[[Category:Java]]
	[[Category:Tips]]		[[Category:Tips]]

wikademia>Wikademia at 07:46, 15 April 2009

2009-04-15T07:46:19Z

← Older revision		Revision as of 07:46, 15 April 2009
Line 1:		Line 1:
			{{ntnes}}
	=When to use methods=		=When to use methods=
	Only use methods when you have a reason to break-up code. You should only use them when the part you are putting into the method has no connection to any other part (or is called at a separate time from it). Methods should finish off a function by themselves. However, long methods can be broken down into shorter methods. They should still, however, follow the steps: no connection, etc.		Only use methods when you have a reason to break-up code. You should only use them when the part you are putting into the method has no connection to any other part (or is called at a separate time from it). Methods should finish off a function by themselves. However, long methods can be broken down into shorter methods. They should still, however, follow the steps: no connection, etc.

wikademia>Wikademia: 22 revisions

2009-04-05T18:32:07Z

22 revisions

← Older revision	Revision as of 18:32, 5 April 2009
(No difference)

wikademia>JavaC++Man: /* Good Comments */

2009-04-03T20:23:07Z

Good Comments

← Older revision		Revision as of 20:23, 3 April 2009
Line 83:		Line 83:

	<pre>		<pre>
	if( x%2 == 0 && x > 0 && x < 1000 ) { ~~// tests for parity, sign, and size~~		// tests for parity, sign, and size
	System.out.println( "x is a positive, even, integer less than 1000" );		if( x%2 == 0 && x > 0 && x < 1000 ) {
			System.out.println("x is a positive, even, integer less than 1000");

	if( x%3 == 0 ) // tests if divisible by 3		if( x%3 == 0 ) // tests if divisible by 3
Line 94:		Line 95:

	<pre>		<pre>
	if( i1 == i2 && i1 == i3 ) // Check if i1 is equal to i2 and i3		if( i1 == i2 \| i1 == i3 ) // Check if i1 is equal to i2 and i3
	{		{
	System.out.println( "~~Yes~~" ); // Print Yes to the command line		System.out.println( "YES!" ); // Print Yes! to the command line
	i1++; // Add 1 to i1		i1= i1 + 1; // Add 1 to i1
	}		}
	</pre>		</pre>

wikademia>JavaC++Man: /* When to press Enter */

2009-04-03T20:20:45Z

When to press Enter

← Older revision		Revision as of 20:20, 3 April 2009
Line 67:		Line 67:
	To make your code look good, you should insert one empty line between methods:		To make your code look good, you should insert one empty line between methods:
	<pre>		<pre>
	public ~~void~~ method1()		public null method1()
	{		{

	}		}

	public ~~void~~ method2()		public null method2()
	{		{

Line 78:		Line 78:
	</pre>		</pre>
	You should make a new line after every statement/declaration. If a statement is too long, you can break it down.		You should make a new line after every statement/declaration. If a statement is too long, you can break it down.

	== Good Comments ==		== Good Comments ==
	Good comments can help make your code look neat. They should tell what you are doing '''overall''', not what you are doing on each line. For example, you can comment an if statement if it is kind of complex, but not every statement has to be commented:		Good comments can help make your code look neat. They should tell what you are doing '''overall''', not what you are doing on each line. For example, you can comment an if statement if it is kind of complex, but not every statement has to be commented:

wikademia>JavaC++Man: /* About Arrays */ errors

2009-04-03T20:19:33Z

About Arrays: errors

← Older revision		Revision as of 20:19, 3 April 2009
Line 5:		Line 5:

	=About Arrays=		=About Arrays=
	Arrays should be used for variables that have something to do with each other. Basically, arrays are a ~~list~~ of variables, and arrays are a variable themselves. Here is how to make an array		Arrays should be used for variables that have something to do with each other. Basically, arrays are a sets of variables, and arrays are a variable themselves. Here is how to make an array set.
	<pre>		<pre>
	[class][~~] [variable~~-name];		[class]() [var-name];
	//Or...		//Or...
	int~~[] myInts~~;		int() var;
	</pre>		</pre>
	To specify the length of an array:		To specify the length of an array:
	<pre>		<pre>
	~~myInts~~=new ~~int[~~LENGTH];		var=new var(LENGTH);
	//Put into one statement		//Put into one statement
	int[] myInts = ~~new~~ int[LENGTH];		int() myInts = int(LENGTH);
	</pre>		</pre>
	LENGTH = array size. It is simply how many items are in the array.		LENGTH = array size. It is simply how many items are in the array.
Line 21:		Line 21:
	You need to initialize each part of the array. To "access" the members of the array:		You need to initialize each part of the array. To "access" the members of the array:
	<pre>		<pre>
	myInts[2]==5;		myInts(2)==3;
	int temp = myInts[3];		int temp = myInts(3);
	</pre>		</pre>
	'''Note''': Do NOT use arrays when the members have nothing to do with each other. This causes ~~messy~~ code!		'''Note''': Do NOT use arrays when the members have nothing to do with each other. This causes code errors!

	=Basic Tips for Improving Code=		=Basic Tips for Improving Code=
	==Tabbing==		==Tabbing==

wikademia>Jtneill: Category:Tips

2008-08-18T05:50:52Z

Category:Tips

← Older revision		Revision as of 05:50, 18 August 2008
Line 105:		Line 105:
	{{1lvlnav\|[[Topic:Java\|Java]]\|[[Important Java Classes]]\|[[Java/Fundamental Exercises\|Fundamental Exercises]]}}		{{1lvlnav\|[[Topic:Java\|Java]]\|[[Important Java Classes]]\|[[Java/Fundamental Exercises\|Fundamental Exercises]]}}
	[[Category:Java]]		[[Category:Java]]
			[[Category:Tips]]

wikademia>Remi: Java Programming Tips moved to Java programming tips: naming conventions

2008-01-14T01:58:32Z

Java Programming Tips moved to Java programming tips: naming conventions

← Older revision		Revision as of 01:58, 14 January 2008
(No difference)