[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: The "make the special type in C" journey and type
- From: Andrew Starks <andrew.starks@...>
- Date: Thu, 3 Oct 2013 18:59:43 -0500
On Thursday, October 3, 2013, liam mail wrote:
At the risk of sounding argumentative, I believe that all if you are proving my point, which is not that in service if some solution that I'm advocating.
It's that the consumer of a library that is designed to provide a special value "type" is left with some acceptable methods to deal with a common question that would otherwise be answered by calling "type", if the value type was native, AND that none of those methods will be consistent between any two libraries.
Yes, I can proffer some more examples and all of you can show me how it isn't wise to do whatever it is I'm doing.
Following this logic, I'd propose that "type" is unnecessary in all cases and could be removed, instead replaced by pcall, whenever we would otherwise need it.
I think that my point more or less stands: extending Lua with values that behave as functions that are imported from the host language is as good as it gets, as far as transparency and interop goes.
Importing values that behave more like new "types" is not transperent, at least in some real-live cases that come up when non 30+ year veterans are attempting to solve the problem in front of them.
-Andrew