The docs are a thing that is often not of many uses.
In this case it extremely bad wording.
Type in this case only refers to the fact, that you can create a variable of this "type".
Numerics are no objects but values only (try it by giving a number to something that wants something of :object like TList.addlast if you trust the docs more than me and others here). The only possibility to get numerics into a TList is make a string out of it and reparse it to an int afterwards ... or like other do, create a Int wrapper object to use it with object based functions.
Another way to proof that is: Create a function that accepts a numeric value and try to modify it. It won't change outside. But it will if you use a true objects. To have this behavior you need to cast it to a reference first (by using variable:int VAR )
This should clearly be stated in the documentation ... but it is one of the significant flaws in the docs at the moment.
Sorry if this made problems to you.
In this case it extremely bad wording.
Type in this case only refers to the fact, that you can create a variable of this "type".
Numerics are no objects but values only (try it by giving a number to something that wants something of :object like TList.addlast if you trust the docs more than me and others here). The only possibility to get numerics into a TList is make a string out of it and reparse it to an int afterwards ... or like other do, create a Int wrapper object to use it with object based functions.
Another way to proof that is: Create a function that accepts a numeric value and try to modify it. It won't change outside. But it will if you use a true objects. To have this behavior you need to cast it to a reference first (by using variable:int VAR )
This should clearly be stated in the documentation ... but it is one of the significant flaws in the docs at the moment.
Sorry if this made problems to you.