Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 2853
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

how to use "fprintf" correctly with "foreach"

acom

 

i have written a script and got what i wanted like below:

 

 

 

*****The original script*****

port=outfile("/home/user/test" "w")

fprintf(port "%s\n" "test1")

fprintf(port "%s\n" "test2")

close(port)

 

 *****The ideal output in /home/user/test*****

test1

test2

 

 i would like to simplify the above script but i have gotten what i didn't expect like below

 

*****the simplified script*****

 testlist=list("test1" "test2")

foreach(testele testlist outfile("/home/user/test" "w") fprintf(port "%s\n" testele)

 close(port)

 

 

*****The bad output in /home/user/test*****

test2

 

 

would you please help me to do someting in the simplified script and get what i want?

 

 

Thanks:) 

Parents
  • Andrew Beckett

    Either:

    testlist=list("test1" "test2")
    port=outfile("/home/user/test" "w")
    foreach(testele testlist
      fprintf(port "%s\n" testele)
    )
    close(port) 

    or:

    testlist=list("test1" "test2")
    foreach(testele testlist
      port=outfile("/home/user/test" "a")
      fprintf(port "%s\n" testele)
      close(port) 
    )

    The second opens the file in append mode. The first opens the port once and then repeatedly writes to it. Take your pick!

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Either:

    testlist=list("test1" "test2")
    port=outfile("/home/user/test" "w")
    foreach(testele testlist
      fprintf(port "%s\n" testele)
    )
    close(port) 

    or:

    testlist=list("test1" "test2")
    foreach(testele testlist
      port=outfile("/home/user/test" "a")
      fprintf(port "%s\n" testele)
      close(port) 
    )

    The second opens the file in append mode. The first opens the port once and then repeatedly writes to it. Take your pick!

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.