This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Problem with cygwin-1.1.2 gawk-3.0.4 [Was: [ANNOUNCEMENT] Updated: gawk-3.0.4]


--- Christian_Jönsson <c.christian.joensson@telia.com> wrote:
-8<-
> 
> The very trivial test1.tcl script is this:
> 
> BASH.EXE-2.04$ less test1.tcl
> set awkCode { { print " "; } }
> 
> exec awk $awkCode
> BASH.EXE-2.04$
> 
> now, it might be my total lack of tcl script writing and thus a PATH
> problem, a cygtcl problem with PATH or awk. hmm, perhaps the link
> awk -> gawk...
> 
> changing and trying again...
> 
> BASH.EXE-2.04$ less test1.tcl
> set awkCode { { print " "; } }
> 
> exec gawk $awkCode
> BASH.EXE-2.04$ cygtclsh80.exe test1.tcl
> gawk.exe: cmd. line:1:  { print "
> gawk.exe: cmd. line:1:          ^ unterminated string
>     while executing
> "exec gawk $awkCode"
>     (file "test1.tcl" line 3)
> BASH.EXE-2.04$ 
> 
> hmm, there is is, the unterminated string problem, test case 1. (and a
> discoverg cygtcl "feauture" :), couldn't handle the awk.exe -> gawk.exe
> link...
> 
> now, changing test2.tcl and trying again...
> 
> BASH.EXE-2.04$ less test2.tcl
> set awkCode { BEGIN { print "\"flow 0" }{ print " "; } }
> 
> exec gawk $awkCode
> BASH.EXE-2.04$ cygtclsh80.exe test2.tcl
> gawk.exe: cmd. line:2: (END OF FILE)
> gawk.exe: cmd. line:2: parse error
>     while executing
> "exec gawk $awkCode"
>     (file "test2.tcl" line 3)
> BASH.EXE-2.04$
> 
> same with test3.tcl...
> 
> BASH.EXE-2.04$ less test3.tcl
> set awkCode { BEGIN {prev=-1; }{ print " "; } }
> 
> exec gawk $awkCode
> 
> BASH.EXE-2.04$ cygtclsh80.exe test3.tcl
> gawk.exe: cmd. line:1:  BEGIN {prev=-1; }{ print "
> gawk.exe: cmd. line:1:                           ^ unterminated string
>     while executing
> "exec gawk $awkCode"
>     (file "test3.tcl" line 3)
> BASH.EXE-2.04$
> 

When communicating between Cygwin and non-Cygwin programs you should `SET
CYGWIN=notty nobinmode' before starting bash, YMMV so it might not help your
case.

Regards,

=====
---
   Earnie Boyd: <mailto:earnie_boyd@yahoo.com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html>
           __Minimalist GNU for Windows__
  Mingw32 List: <http://www.egroups.com/group/mingw32/>
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]