[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
SAFEty and the Cross Referencing of BLASTs
- To: <michael@xxxxxxxxxxx>
- Subject: SAFEty and the Cross Referencing of BLASTs
- From: Mark S. Miller <vlad!mark>
- Date: Wed, 5 Dec 90 17:24:54 PST
- Cc: <xtech@xxxxxxxxxxx>
- In-reply-to: <Michael>,13 PST <9012031118.AA09923@xanadu>
Date: Mon, 3 Dec 90 03:18:13 PST
From: xanadu!michael (Michael McClary)
> From vlad!mark Sat Dec 1 20:47:34 1990
> If a [member] function is declared SAFE, then it may not allocate any
> memory, it may not BLAST anything which it doesn't catch, and it may
> only call [member] function which are themselves declared SAFE. []
Why the restriction to member functions? If a global function causes
a memory allocation or a BLAST, it's just as unsafe.
Sorry, I should have explained my notation. By "[member] function" I
meant "function or member function". The "member" was in the zero-or-
one-instance-square-brackets that we've seen in various BNF
extensions.