So a simple matter variable might be a single number. A structure is a collection of related variables in one place, like an address. Semantically it is treated as a single variable. An object is a structure with functions that operate on it.
number, street name, street type, city, province, country, postal code
suite number
etc
those could all be member variables in an Address object
The program can then pass the object around atomically instead of as lots of little parts
so I can have a function like "sendMail" which takes two parameters, 1. an address, 2. a message to send.
or maybe the message is an object and I can tell the message "accept this address as your destination" and then I can tell it "now send yourself to that address"
But where object-oriented programming really gets useful is when you have polymorphism and inheritance.
inheritance is where you declare that a certain kind of object is a sub-type of a larger class. polymorphism is where the methods of the subtype automatically replace the methods of the super-type.
So I might have an object called "Animal" and a sub-type called "Cat" and another called "Dog". Each of them has a "feed" function which I can call even if I don't know if my variable is a cat or a dog or some other kind of animal.
That makes the code simpler (when done properly) because you can write small, elegant functions that can handle all the future cases you might encounter.
just to make things funner, arrays can be stored (or referenced) in variables and also arrays contain variables, and also arrays can be objects (they are in Java and probably are in AHK but aren't in C)
@Cerberus because it offers no protection for getting something wrong. The first syntax uses punctuation to clearly indicate which are keys, which are values. The second relies on position.
If you make a mistake editing that code, you might end up with a bunch of keys stored as values and vice versa
I mean, I wrote code that worked like that, it was convenient for a use case, but it's ugly. The only reason I did it was because the first syntax wasn't available in Java.
It may pick common convention A is there is no simpler way of doing what it does, but it may not follow convention B if it can think of a simpler way of doing what B does.
Mm sometimes, but it does have consistency in mind usually.
The one thing where it is lacking consistency in a bad way is when variables need to be enclosed in percentage signs and when they don't.
And the same for strings and quotation marks, mutatis mutandis.
in Javascript, variables can start with almost any character. If you name your variable $blah, then that is its name and you will always refer to it as $blah
Both YoutubeTime and Tempclip are variables. I believe they wouldn't require decorations in Javascript in that situation, would they? But sometimes variables do require decorations in Javascript, don't they?
> #DerefChar # ; Change it from its normal default, which is %. #Delimiter / ; Change it from its normal default, which is comma. #EscapeChar \ ; Change it to be backslash instead of the default of accent (`).
English Language & Usage: Multi-Layer…
English Language & Usage: Multi-Layer…