X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=hd 2FMvsAsAGJtGOh7xbgAn0B2cgf3nzVmSBeS7VJCKDkLi1iAspxnTSJBY7XT/dzTL wvHEqUP0HqsCqR9tbAN7mIgaDLdFhgWBLf648EerG0U5kIbw3W3q6hYqe4Iwn9F7 hAGnBA02nie6Y4NzdOxEqDZbkV5QV18X2tib3L/oM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=Bsx23Afy EMpmwvMEsHVlre660ko=; b=pSX3My5uT8F/u0vMpGQeRNLl8zCTHl5TsQ2Et3DP tFswLW4siwnoNwxtDsyAIEOZKgDu7DMoF1oXgVfPofJiQHPk1iq1fPsMqcJhCu5c PqKpBVBF0LJntSjaFFBmJfKIhD3fpUUPVCQ8cfiwAXuTqH9byy7LNDpmsN783bSk iVo= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-5.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.224.16.66 with SMTP id n2mr4934048qaa.29.1365081321462; Thu, 04 Apr 2013 06:15:21 -0700 (PDT) In-Reply-To: <515D78B1.60209@farance.com> References: <20130404170527 DOT 3708 AT binki> <20130404085538 DOT GE25170 AT calimero DOT vinschen DOT de> <515D78B1 DOT 60209 AT farance DOT com> Date: Thu, 4 Apr 2013 09:15:21 -0400 Message-ID: Subject: Re: But it is cygwin related. From: Earnie Boyd To: Andrey Repin Content-Type: text/plain; charset=UTF-8 On Thu, Apr 4, 2013 at 8:57 AM, Frank Farance wrote: > > I haven't posted in a long while, but the question seems reasonable and > relevant to cygwin. If one were writing assembler code to be compatible > with cygwin, one would need the answer to the question originally posed. I > don't see this as a question about win32 APIs (which might be answered by > your link above), it is a compatibility question ... certainly, we would > have thought about it this way when writing a mix of C and assembler code 40 > years ago on UNIX systems. > The OP was related to "How to program". From cygwin.com/lists.html we have ~~~~~~ Finally, make sure when you send a message to a Cygwin list that it actually has something to do with Cygwin. What do we mean by that? Well, if you can't install the Cygwin C compiler, then that has something to do with Cygwin. If you don't know C very well and need some pointers on writing a program, that really has nothing to do with Cygwin. If you are trying to run the Cygwin version of bash (the standard UNIX shell) and it hangs, then that's probably a Cygwin problem. If you can't figure out how to set up a command alias in bash, that's not a Cygwin question. These Cygwin questions are considered "on topic". The non-Cygwin questions are considered "off topic". ~~~~~~ Which clearly states that "How to program" posts are off-topic for this list and any other cygwin list. -- Earnie -- https://sites.google.com/site/earnieboyd -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple