From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <90633615ea9185870208e11290f42eb7@proxima.alt.za> To: lucio@proxima.alt.za, 9fans@9fans.net From: Lucio De Re Date: Fri, 28 Oct 2011 14:08:07 +0200 In-Reply-To: <755c0af9d04658f3d757fd5e5f29dd92@proxima.alt.za> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-yjwxjaudelelvgtlgktyalqqnc" Subject: Re: [9fans] nanosleep()? Topicbox-Message-UUID: 3bc2a4fa-ead7-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-yjwxjaudelelvgtlgktyalqqnc Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Oops, a heavy handed comment intended to amuse Charles rather than be critical of the Go Authors. I do not intend to offend anyone and I apologise if I did. ++L --upas-yjwxjaudelelvgtlgktyalqqnc Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from proxima.alt.za (dsl-144-185-101.telkomadsl.co.za [41.144.185.101]) (authenticated bits=0) by mumble.proxima.alt.za (8.14.3/8.14.3) with ESMTP id p9SBu6VQ011919 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 28 Oct 2011 13:56:07 +0200 (SAST) Message-ID: <755c0af9d04658f3d757fd5e5f29dd92@proxima.alt.za> To: charles.forsyth@gmail.com, lucio@proxima.alt.za, 9fans@9fans.net Subject: Re: [9fans] nanosleep()? From: Lucio De Re Reply-to: lucio@proxima.alt.za Organization: Proxima Research & Development Date: Fri, 28 Oct 2011 14:05:25 +0200 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mumble.proxima.alt.za [192.96.32.140]); Fri, 28 Oct 2011 13:56:08 +0200 (SAST) X-Filter: OK > ppmaps might just work (depending on libmach, i suppose). > also, although it's supposed to profile at "regular" real-time intervals, > it seems to assume that regularity will just happen. perhaps it does. I do wonder who assembled all these tools, I have found enough mixtures of Plan 9 compatibilities and Posix-isms to cause me indigestion. But at this point I only want to eliminate compilation errors in the Go build procedure under Plan 9, I don't really care if some tools do not function as required, as long as they are not essential to the build. On the other hand, if the tools can be made to work correctly besides compiling successfully, it will improve the likely acceptance of Go and that ought to be a good thing. ++L --upas-yjwxjaudelelvgtlgktyalqqnc--