Why there is no pod literal? sys::, concurrent::, this::?
sys::
concurrent::
this::
I have not need for pod literal. I ask just for consistency.
Consider slightly modified example from docs
Pod.find("icoms").file(`/x16/error.png`) // Showing some error dialog
Yes, icoms. Looks like we failed at failing. This error might be very difficult to hit. icoms:: or icoms::# would do much better here.
icoms::
icoms::#
Well in the case of file lookup, I would recommend using a URI literal:
`fan://icons/x16/error.png`.toFile
Pod literals might be nice, they also dove tail into ability to get type of enclosing type in a static method (another discussion).
But I am not in a rush to add those - they would useful, but I don't consider them a critical need.
Login or Signup to reply.
Akcelisto Tue 11 Jan 2011
Why there is no pod literal?
sys::,concurrent::,this::?I have not need for pod literal. I ask just for consistency.
vkuzkokov Thu 13 Jan 2011
Consider slightly modified example from docs
Pod.find("icoms").file(`/x16/error.png`) // Showing some error dialogYes, icoms. Looks like we failed at failing. This error might be very difficult to hit.
icoms::oricoms::#would do much better here.brian Thu 13 Jan 2011
Well in the case of file lookup, I would recommend using a URI literal:
Pod literals might be nice, they also dove tail into ability to get type of enclosing type in a static method (another discussion).
But I am not in a rush to add those - they would useful, but I don't consider them a critical need.