X-Spam-Check-By: sourceware.org Message-ID: <44F4B31C.7010202@gmail.com> Date: Tue, 29 Aug 2006 17:35:24 -0400 From: Tristen Hayfield User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problem when using variable assignment, backticks in shell script References: <017630AA6DF2DF4EBC1DD4454F8EE29708D75075 AT rsana-ex-hq1 DOT NA DOT RSA DOT NET> <44F4AEB3 DOT 7769D22D AT dessent DOT net> In-Reply-To: <44F4AEB3.7769D22D@dessent.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 One may also do: read x < temp in bash Tristen Brian Dessent wrote: > "Silva, Russell" wrote: > >> x=`/usr/bin/cat < temp`; > > I don't know what is causing your problem. I ran your testcase several > times and never saw a failure, but from your description it seems like > it's the kind of thing that might occur very rarely. > > My only suggestion is that if your true desire is to actually read the > contents of a file into a variable, then the above construct is a fairly > expensive way of doing it. This requires a fork/exec (an operation > which is extremely slow under cygwin) of /bin/cat, whose purpose is only > to read from one fd and write to another. If you can live with a > bash-specific (?) construct, then x=$(< temp) should cause the same > effect but much more efficiently, as the shell itself just reads the > file without invoking any subprocesses. > > Brian > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/