Lines Matching full:sense
95 it made sense to roll out the use of ReturnAddressPtr a little further into
2060 makes the most sense.
4099 Um. Yeah, this this pretty pointles and makes no sense at all. I officially
9413 important, so it makes sense to apply the assertions in release builds
10361 more sense and eliminate special cases for null prototypes.
14342 value now encapsulated it will likely make sense to migrate the functionality
14347 At this stage it will likely make sense to rename JSValuePtr to JSValue.
25718 a specialization made no sense, since CallIdentifier is not an integer,
28786 itself from the destructor; that doesn't even make sense.
31638 d->registers, but that makes no sense (they are local variables, not
33349 - introduce a TypeInfo class, for holding per-type (in the C++ class sense) date in StructureID
39553 Ref/deref global data to give checking for globalData.refCount() some sense.
