Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!pilchuck!dataio!uw-entropy!uw-june!brian
From: brian@uw-june.UUCP (Brian Bershad)
Newsgroups: comp.lang.c++
Subject: why can't inline handle loops?
Message-ID: <3004@uw-june.UUCP>
Date: Sun, 23-Aug-87 03:46:26 EDT
Article-I.D.: uw-june.3004
Posted: Sun Aug 23 03:46:26 1987
Date-Received: Tue, 25-Aug-87 00:39:14 EDT
Reply-To: brian@uw-june.UUCP (Brian Bershad)
Distribution: world
Organization: U of Washington, Computer Science, Seattle
Lines: 17
Keywords: inline, loops

I can understand the motivation (if it loops, it takes a while, so
why bother with inline expanding), but the restriction seems arbitrary.

Consider a spinlock for example:
	in the normal case, it returns immediately.  Only rarely will
	the lock be held and will spinning be required.

If it is an arbitrary restriction, what breaks if I take out the
check for looping in dcl3.c?



-- 
brian@june.cs.washington.edu                	Brian Bershad
{ihnp4,decvax,ucbvax}!uw-beaver!uw-june!brian   Dept. of Computer Science, FR-35
						University of Washington
                                                Seattle, WA 98195