I stumbled across the following comment:
/*
Jeff, I weakened the following assert because we
*want* to represent no tabstops as an empty string.
If this isn't safe, let me know. -- PCR
*/
UT_ASSERT(p[1] /* && *p[1] */); // require value for each name
It seems that we have a bunch of other empty props now too, like
TF's new 'display' property.
Now, I've been working on some field code (bug: start typing in
italics and insert a field; the field does not appear in italics!)
and in fixing this bug, I get the corresponding assert in the
attributes code.
That's because a field has an empty string "" in its param attribute.
Do we really want that? If so, I'll weaken the attribute assert too.
pat
