User Tools

Site Tools


macros:type:object

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
macros:type:object [2018/01/28 11:12] – ↷ Links adapted because of a move operation icke_siegenmacros:type:object [2018/06/25 13:24] (current) icke_siegen
Line 3: Line 3:
 As this is a very simplified documentation, we may retreat to the following statement: while 'primitive' values - like [[string|strings]], [[single|singles]] etc. - contain only one value, objects are more complex. A very basic example is given in the [[macros:types|overview on types]]: imagine an address which is composed maybe of a street name, a number, a zip code, and a city - then the whole thing is the address object, and the individual values are the properties of this object. As this is a very simplified documentation, we may retreat to the following statement: while 'primitive' values - like [[string|strings]], [[single|singles]] etc. - contain only one value, objects are more complex. A very basic example is given in the [[macros:types|overview on types]]: imagine an address which is composed maybe of a street name, a number, a zip code, and a city - then the whole thing is the address object, and the individual values are the properties of this object.
  
-In the context of Titan macros, you'll most likely see objects like [[.object:handle|handles]], [[timestamp|timestamps]], and some more. They are explained in more detail in separate articles - see the indivitual link further down.+In the context of Titan macros, you'll most likely see objects like [[..:identifier:handle|handles]], [[.object:timestamp|timestamps]], and some more. They are explained in more detail in separate articles - see the indivitual link further down.
  
 Also, there seems to happen implicit parsing/conversion. E.g. the function [[macros:function:math.min]] expects two objects as input - but in the example [[macros:example:doublechasespeed]] it also works with a number like 3600.0: Also, there seems to happen implicit parsing/conversion. E.g. the function [[macros:function:math.min]] expects two objects as input - but in the example [[macros:example:doublechasespeed]] it also works with a number like 3600.0:
Line 30: Line 30:
  
 <nspages macros:type:object -h1 -simpleList -textPages=""> <nspages macros:type:object -h1 -simpleList -textPages="">
 +However the most important object type in Titan is more in-depth explained as [[macros:identifier:handle]].
  
 == Objects are also mentioned in == == Objects are also mentioned in ==
  
 {{backlinks>.}} {{backlinks>.}}
 +
  
 ~~DISCUSSION~~ ~~DISCUSSION~~
  
macros/type/object.1517137954.txt.gz · Last modified: 2018/01/28 11:12 by icke_siegen

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki