rfc:structured_object_notation
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:structured_object_notation [2016/07/31 08:52] – midorikocak | rfc:structured_object_notation [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 86: | Line 86: | ||
Let's have one class called B, similar to above example. | Let's have one class called B, similar to above example. | ||
- | < | + | < |
- | Class B{ | + | class B{ |
// No way to define order of methods | // No way to define order of methods | ||
Line 119: | Line 119: | ||
Instead of instantiating objects on the fly, here I propose a structured definition of an object using this syntax: | Instead of instantiating objects on the fly, here I propose a structured definition of an object using this syntax: | ||
<code php> | <code php> | ||
- | + | object | |
- | Object | + | |
$world = " | $world = " | ||
// allowed methods comes after method definition | // allowed methods comes after method definition | ||
Line 140: | Line 139: | ||
}; | }; | ||
} | } | ||
- | + | </code> | |
- | < | + | |
An object can be instance of a class, if it's not defined, is instance of an anonymous class. | An object can be instance of a class, if it's not defined, is instance of an anonymous class. |
rfc/structured_object_notation.1469955124.txt.gz · Last modified: 2017/09/22 13:28 (external edit)