Let's say we would get those implemented and we could have a module like this:
#Xojo coupon code code
If this would be implemented, you could skip all those getter functions and the compiler could make much better code to just lookup the global EndOfLine property easier and skip it for the shared properties. The properties could have an attribute to mark them public to get, but private to set. The constructor may only access things in the module and should be called before app.open. So we need a kind of constructor for modules like in feedback case 24018. For example a module could define them and in a Constructor for the module they could be assigned. All those shared properties could be real properties for the compiler, which could be marked to be read only for access from outside. Beside with EndOfLine, they could help us for our own code. Looking into EndOfLine reminds me to two feature requests, I'd like to see implemented in a future Xojo version. A line like this may speed up access to EndOfLine :įollowing access is at least double the speed, so if that is a bottleneck for you, you can optimize it!īut only worth it, if you call EndOfLine a lot in loops within your code. And they seem to be implemented differently, so some return the same string always, while others just create a new string each time.ĭue to the fact that using EndOfLine invokes two functions to get the object and then the string, it makes sense to cache the value. Update: Introspection shows those are shared properties, but computed.
![xojo coupon code xojo coupon code](https://www.nuvotech.co.uk/images/xojo-design-awards-badge.png)
The individual functions Android, LF, iOS, CR, Unix, macOS, CRLF, Windows are shared methods (or properties?) on the class.
![xojo coupon code xojo coupon code](https://cdn4.couponarea.com/logos/l/j/jovianinternational.com.jpg)
If you use it in a string operation, it may invoke one of the operator methods like Operator_Convert to get the string for the current platform. This is optimized and we can verify in the debugger that we get the same object each time. When you use EndOfLine in the code as value and not as class, you call a global function called EndOfLine returning the EndOfLine object. This is of course an implementation detail and could change.