You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The determination of which elements of the body are tags and which are statements is made prior to any macro expansion of that element
But not, afaict, how it is determined whether something is a tag or not. Glossary sez:
go tag n. the symbol or integer that, within the lexical scope of a tagbody form, names an exit point established by that tagbody form
So, presumably, an element is a tag iff it is a symbol or integer. But this should be specified in the definition of tagbody itself, not just in the glossary.
The text was updated successfully, but these errors were encountered:
The tagbody page describes tags as "go tag"s with a link to the glossary in its Arguments and Values. I think that's sufficient. I mean, analogously the defun page does not itself explicitly state what a function name is.
Spec sez:
But not, afaict, how it is determined whether something is a tag or not. Glossary sez:
So, presumably, an element is a tag iff it is a symbol or integer. But this should be specified in the definition of tagbody itself, not just in the glossary.
The text was updated successfully, but these errors were encountered: