Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Gentlefish]

That's exactly it.

Your prof said you're not allowed to modify the class. But you're allowed to modify objects using class functions.

[Orange Wizard]

...no? not at all, python's where i learned the distinction

an object is an instantiation of a class

Whaaaaaaaaaaaat

That's a completely different way of thinking about it than I'm used to

[Orange Wizard]

I'm... increasingly unsure.

An instance of something is the same as the thing of which it's an instance, apparently

[3man75]

Spoiler (click to show/hide)

[code]System.out.println ("Okay lets make a regular account. Please Give me your name.");
            String nameOfAccount = namingAccount.nextLine();
            //HOW TO NAME THE ACCOUNT AND SEND IT TO THE bankAccounts
            
            //BankAccount.setName(nameOfAccount);
            
            BankAccount placeholder = new BankAccount();
            
            placeholder.setName(nameOfAccount);
            [code]

Sorry but last question: How do I add the object to the arraylist?[/code]

[itisnotlogical]

I'm... increasingly unsure.

An instance of something is the same as the thing of which it's an instance, apparently

It's useful to think of it in terms of real-world objects.

Dogs (the class) are something with fur, four legs, two eyes and a tail.

Some dogs (instances) are chihuahuas, dalmations, black labs, etc.

Fun fact: I wrote like ten different comparisons before hitting on one that wasn't confusing and unhelpful.

[Putnam]

apples

[itisnotlogical]

I started with mailboxes because that's the traditional metaphor for variables. It wasn't as helpful for explaining classes.

[Putnam]

and inheritance is like how apple is subclass of fruit and composition where core is part of apple but not grape.

and apple can be like Apple('green','sorta sour','crispy') or Apple('red','bittersweet','sorta mushy') though that's awfully human-centric way of thinking about it. just remember: more can be said about an apple than every apple

also, one more thing: RED DELICIOUS IS GROSS YO

time to go to bed i think

[Orange Wizard]

I'm just going to stick with functional programming

[Putnam]

why's it always gotta be so complicated

i was about to say go with procedural, but they make that an analogy to OOP for some utterly god-forsaken reason

the sun does not shine on whoever comes up with these labels

...huh, that's probably literally true, now that i think of it

NERDS

EDIT:

Code: [Select]

APawn* const Pawn = GetPawn();
FVector velocity = Pawn->GetVelocity();
FTransform transform = Pawn->GetTransform();
that second line causes unreal engine 4 to crash when I try to convert it to a blueprint for UI design purposes

what a feeling that is, to begin work on something and immediately screw it up so bad that it crashes code made by some of the best engine writers in the industry

it works fine as C++, really quite perfect, but when I convert it to blueprint it doesn't work

to that end, screw blueprints, i'm sticking with c++

[Reelya]

I'm... increasingly unsure.

An instance of something is the same as the thing of which it's an instance, apparently

It's useful to think of it in terms of real-world objects.

Dogs (the class) are something with fur, four legs, two eyes and a tail.

Some dogs (instances) are chihuahuas, dalmations, black labs, etc.

Fun fact: I wrote like ten different comparisons before hitting on one that wasn't confusing and unhelpful.

That's potentially confusing, because dog breeds may be child classes of dog. e.g. "chihuahuas are a type of dog" is saying "class chihuahua derives from class dog" in OOP-speak. Whereas "this is my dog (an object) he is a chihuahua" (a class, which is also a subclass of the "dog" class).

[TheBiggerFish]

Spoiler (click to show/hide)

[code]System.out.println ("Okay lets make a regular account. Please Give me your name.");
            String nameOfAccount = namingAccount.nextLine();
            //HOW TO NAME THE ACCOUNT AND SEND IT TO THE bankAccounts
            
            //BankAccount.setName(nameOfAccount);
            
            BankAccount placeholder = new BankAccount();
            
            placeholder.setName(nameOfAccount);
            [code]

Sorry but last question: How do I add the object to the arraylist?[/code]

...
No.

Code: [Select]

System.out.println("Please input the name of the account holder.");

String name = namingAccount.nextLine();

//By the way, you really shouldn't name your Scanner that,
//it's not at all relevant to what it actually does.

arraylistvar.add(new BankAccount(name));

//You have this constructor, right?  Use it.  If you don't, make it.
//Also you can do this. 
//Though you'll need to keep track of where your variable goes in the array somewhere.

Here's how I think of classes/instances:A class describes the shared features of something.  A (properly-instantiated) instance of a class is something that has those features.  Those features may be instances of other classes, etc. etc..

For instance, a book has a title, an ISBN, an author, etc., and pissibly a person to whom it's loaned out.  That person has a name, and age, and some books they own or rent.

[Skyrunner]

I'm... increasingly unsure.

An instance of something is the same as the thing of which it's an instance, apparently

It's useful to think of it in terms of real-world objects.

Dogs (the class) are something with fur, four legs, two eyes and a tail.

Some dogs (instances) are chihuahuas, dalmations, black labs, etc.

Fun fact: I wrote like ten different comparisons before hitting on one that wasn't confusing and unhelpful.

That's potentially confusing, because dog breeds may be child classes of dog. e.g. "chihuahuas are a type of dog" is saying "class chihuahua derives from class dog" in OOP-speak. Whereas "this is my dog (an object) he is a chihuahua" (a class, which is also a subclass of the "dog" class).

I'd feel that dog breeds is a bad example of subclassing. Are different breeds really so different that you want subclasses, or is it better to store attributes in data and populate it with a factory? :v

[Reelya]

To be honest, almost all examples of sub-classing are bad examples. The mechanism itself is very over-rated, and leads to poor code that's hard to maintain. It's just an example.

For example, the canonical "person, student, teacher" example is very obviously flawed. What do you now do if a teacher themselves enrols in a subject?

[Rose]

You don't need subclasses for dog breeds.