#Greenfoot arrays code#

The code within the method isGreater uses the variable aNumber to determine if the value is greater than the constant MAX_VALUE.The method isGreater is expecting an integer value, so it ‘catches’ the value and stores it in the parameter called “aNumber”.We call the method isGreater and pass the value stored in theInteger to it:.As its name indicates, this stores an integer in it, for later use. First, we have a variable called theInteger.Let’s look a little closer at how this works.

code that works out an integer value theInteger here eg: * a method to compare an integer with the MAX_VALUE The method’s signature would be:Įxample code for this method may look like: The author of the method decides on the return type.Ī method isGreater might input an int and compare it to a constant (a fixed value) and then return a boolean value – true if the int is greater than the constant, false if it is not. The return type is dependent on the purpose of the method. The example method findSmallest has a return type that is also “int”. The names follow the normal rules for naming variables, so we use camelCase and we don’t use special characters in the name. Note that there are no spaces in the names. Has two parameters, number1 and number2, that are both of type int. Int findSmallest(int number1, int number2) If they do have parameters, then these parameters are separated by commas, and each is preceded by the type of the parameter.Įach parameter needs a type and a name that will be used to store the value passed to the method. Methods don’t necessarily need to have any parameters. In the method signature we specify what type of data is required, and how many parameters. Methods can also take in data to use in the method or class, via the parameters of the method. a more complex type such as an Array, Actor or other class.a primitive type such as int or double or.Methods have a return type that can be either by using the name of the object and dot notation, then the method call, as we did in the previous module.by using the name of the method IF the method is in the same class as the calling code OR.Methods are the parts of classes that do something. Along the way we will use method signatures extensively, so this module begins with a review of method and constructor signatures. In this module, we will look closer at the options for creating objects, but we will also look at the methods and the properties (instance variables) of classes/objects. we have created objects by using the ‘new’ keyword.we have used the Greenfoot environment to visually create an object.So far in this unit, we have created objects in two ways: In object-oriented programming, we create classes that act as templates, from which objects are created. Watch ‘Concept Video 10-2 Method Overloading Watch ‘Concept Video 10-1 Review of Module 9 Internet access to access your lecture, and any other material.“Introduction to Programming with Greenfoot” textbook and support files.

Files in “Module10” folder on MySCU site.

#Greenfoot arrays free#

The free Greenfoot programming environment.

This module is all about how we can create one class that has properties that allow individual objects to behave and look somewhat different from each other. If you have not completed the work up until now, please go back and make sure you are familiar with it all, before going further. Note that it is assumed that you have completed the work up until this point, and are familiar with creating objects, using constructors, creating methods and using return types.