Java/Iterable - Revision history

Admin: /* Implementation - Unsorted Table Map */

2017-06-25T09:52:02Z

Implementation - Unsorted Table Map

← Older revision		Revision as of 09:52, 25 June 2017
Line 19:		Line 19:
	==Implementation - Unsorted Table Map==		==Implementation - Unsorted Table Map==

	See [[Maps/UnsortedTableMap]] ~~or [[Maps~~/~~Iterables]]~~		See [[Maps/UnsortedTableMap]] for another example of iterables/iterators in action. This class requires defining three pairs of classes: Iterator and Iterable objects for keys, values, and key-value pairs.

	==Implementation - Tree Iterator==		==Implementation - Tree Iterator==

Admin: /* Implementation - Tree Iterator */

2017-06-25T09:51:25Z

Implementation - Tree Iterator

← Older revision		Revision as of 09:51, 25 June 2017
Line 16:		Line 16:
	* E next()		* E next()
	* void remove()		* void remove()

			==Implementation - Unsorted Table Map==

			See [[Maps/UnsortedTableMap]] or [[Maps/Iterables]]

	==Implementation - Tree Iterator==		==Implementation - Tree Iterator==
Line 109:		Line 113:
	public Iterator<E> iterator() { return new ElementIterator(); }		public Iterator<E> iterator() { return new ElementIterator(); }
	</pre>		</pre>




	=Flags=		=Flags=

Admin: /* Iterable vs Iterator */

2017-06-23T07:57:19Z

Iterable vs Iterator

← Older revision		Revision as of 07:57, 23 June 2017
Line 5:		Line 5:
	===Iterable vs Iterator===		===Iterable vs Iterator===

	Iterable is a generic ~~dead-fish~~ approach to ~~providing items; it's like~~ the ~~endless breadsticks at Olive Garden. Don't ask~~ where ~~the breadsticks come from~~ or ~~if there will be more breadsticks~~, just ~~shut your face and keep eating breadsticks. This is as easy as putting all your Node objects or your elements or your whatevers in a list, and returning~~ the ~~list~~. ~~The user is just gonna keep eating whatever~~ you ~~set in front of them, hope they're~~ just ~~breadsticks~~.		Iterable is a generic approach to getting an iterator. It enables an object to support for-each syntax. It is not concerned with how the iterator works, where it starts or stops, etc. It just returns the iterator. If you implement Iterable<E> you just need to be able to provide an Iterator<E>.

	Java API Docs: Iterable: http://docs.oracle.com/javase/7/docs/api/java/lang/Iterable.html		Java API Docs: Iterable: http://docs.oracle.com/javase/7/docs/api/java/lang/Iterable.html

Admin: /* Iterable vs Iterator */

2017-06-18T19:59:26Z

Iterable vs Iterator

← Older revision		Revision as of 19:59, 18 June 2017
Line 6:		Line 6:

	Iterable is a generic dead-fish approach to providing items; it's like the endless breadsticks at Olive Garden. Don't ask where the breadsticks come from or if there will be more breadsticks, just shut your face and keep eating breadsticks. This is as easy as putting all your Node objects or your elements or your whatevers in a list, and returning the list. The user is just gonna keep eating whatever you set in front of them, hope they're just breadsticks.		Iterable is a generic dead-fish approach to providing items; it's like the endless breadsticks at Olive Garden. Don't ask where the breadsticks come from or if there will be more breadsticks, just shut your face and keep eating breadsticks. This is as easy as putting all your Node objects or your elements or your whatevers in a list, and returning the list. The user is just gonna keep eating whatever you set in front of them, hope they're just breadsticks.

			Java API Docs: Iterable: http://docs.oracle.com/javase/7/docs/api/java/lang/Iterable.html
			* Iterator<E> iterator()

	An Iterator provides you with an actual object interface that makes it work like a scanner - hasNext(), next(), remove(). It is nicer but it takes more work - you gotta define your own class that extends the iterator class.		An Iterator provides you with an actual object interface that makes it work like a scanner - hasNext(), next(), remove(). It is nicer but it takes more work - you gotta define your own class that extends the iterator class.

			Java API Docs: Iterator: https://docs.oracle.com/javase/7/docs/api/java/util/Iterator.html
			* boolean hasNext()
			* E next()
			* void remove()

	==Implementation - Tree Iterator==		==Implementation - Tree Iterator==

Admin: /* Flags */

2017-06-18T19:57:18Z

Flags

← Older revision		Revision as of 19:57, 18 June 2017
Line 107:		Line 107:
	=Flags=		=Flags=

			{{CSFlag}}

	[[Category:Java]]		[[Category:Java]]
	[[Category:OOP]]		[[Category:OOP]]
	[[Category:Iterators]]		[[Category:Iterators]]

Admin: /* Flags */

2017-06-18T19:57:07Z

Flags

← Older revision		Revision as of 19:57, 18 June 2017
Line 110:		Line 110:
	[[Category:Java]]		[[Category:Java]]
	[[Category:OOP]]		[[Category:OOP]]
	[[Category:~~Iterable~~]]		[[Category:Iterators]]

Admin at 19:55, 18 June 2017

2017-06-18T19:55:52Z

@@ Line 1: / Line 1: @@
-First, we have a high level interface called Tree, which has a method called positions() returning an iterable container with all positions in the tree:
+==Notes==
 <pre>
 public interface Tree<E> extends Iterable<E> {
 	public Iterable<Position<E>> positions();
+}
 </pre>
-Once the interface defines that, any concrete classes implementing that interface must implement that method. Here is a concrete class that implements the Tree interface, and implement s a position() method to assemble all of the positions in the tree:
+As noted above, an Iterator is a full fledged wrapper object that works like a scanner - next, hasNext, remove, etc. The Iterable is a more dumbed down, straight-up iterable container. The whole iterable thing, all at once.
 <pre>
@@ Line 51: / Line 74: @@
 </pre>

Admin at 18:42, 18 June 2017

2017-06-18T18:42:38Z

← Older revision		Revision as of 18:42, 18 June 2017
Line 55:		Line 55:
	[[Category:Java]]		[[Category:Java]]
	[[Category:OOP]]		[[Category:OOP]]
	[[Category:~~iterable~~]]		[[Category:Iterable]]

Admin at 18:42, 18 June 2017

2017-06-18T18:42:30Z

← Older revision		Revision as of 18:42, 18 June 2017
Line 51:		Line 51:

	</pre>		</pre>


			[[Category:Java]]
			[[Category:OOP]]
			[[Category:iterable]]

Admin at 18:41, 18 June 2017

2017-06-18T18:41:53Z

← Older revision		Revision as of 18:41, 18 June 2017
Line 1:		Line 1:
	First, we have a high level interface ~~that defines a particular behavior for a~~ Tree ~~class~~, which is an iterable container ~~that contains~~ all ~~of the~~ positions in the tree:		First, we have a high level interface called Tree, which has a method called positions() returning an iterable container with all positions in the tree:

	<pre>		<pre>