Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <00a501bfdf74$37bb85e0$c7a7b5d4@p4kpm> From: =?iso-8859-1?Q?Christian_J=F6nsson?= To: "Corinna Vinschen" , "Earnie Boyd" Cc: References: <20000626124554 DOT 28273 DOT qmail AT web108 DOT yahoomail DOT com> <007a01bfdf6d$3feeb0e0$c7a7b5d4 AT p4kpm> <39575AD4 DOT 69C6392E AT cygnus DOT com> Subject: Re: Problem with cygwin-1.1.2 gawk-3.0.4 [Was: [ANNOUNCEMENT] Updated: gawk-3.0.4] Date: Mon, 26 Jun 2000 15:40:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6600 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id JAA27623 well, the my guess right now is that the problem has with passing of chars between tcl and gawk. So, in that view, the problem *is* isolated. Earnie suggested experimenting with escaping and that's what I did. The "resulting, but not equivalent to unix/linux variants is this: BASH.EXE-2.04$ less test1.tcl set awkCode { { print "\" \""; print "\"flow \"" $2;} } exec awk $awkCode BASH.EXE-2.04$ and the original had this: BASH.EXE-2.04$ less test1-orig.tcl set awkCode { { print " "; print "\"flow " $2;} } exec awk $awkCode BASH.EXE-2.04$ I got my real problem "solved", I could run my test suite and had some differences that looked like this: ../../ns test-suite-red.tcl flows_unforced QUIET 3,4c3,4 < < "flow 1 --- > " " > "flow "1 21,22c21,22 < < "flow 2 --- > " " > "flow "2 39,40c39,40 < < "flow 3 --- > " " > "flow "3 Test output differs from reference output So, I'll leave it at this. There's some kind of problem related to passing chars between tcl and gawk under cygwin. Thanks for the help this far. Cheers, /ChJ ----- Original Message ----- From: "Corinna Vinschen" To: "Christian Jönsson" Cc: Sent: Monday, June 26, 2000 3:29 PM Subject: Re: Problem with cygwin-1.1.2 gawk-3.0.4 [Was: [ANNOUNCEMENT] Updated: gawk-3.0.4] > Christian Jönsson wrote: > > > > I have not made any awk script, I think the problem lies in passing some chars between tcl and awk. could be tcl could be gawk, could even by cygwin but that's a guess. In this case, it's either the char " or the " in followed by blank char. > > > > As for trying escaping like you mention below, what do you suggets for the tcl script: > > > > set awkCode { { print " "; } } > > > > exec awk $awkCode > > I would suggest to do what is opportune in that situation: > > Try to ISOLATE the problem. Try calling gawk without using Tcl > and try calling Tcl without gawk. > > As Chris has already mentioned, tcl/tk has only a bit of Cygwin > support so you might have problems in interacting, similar to any > interacting between Cygwin tools and native w32 tools. > > Corinna > > -- > Corinna Vinschen > Cygwin Developer > Cygnus Solutions, a Red Hat company > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com