zsh-users
 help / color / mirror / code / Atom feed
From: Carlos Carvalho <carlos@fisica.ufpr.br>
To: zsh-users@sunsite.dk
Subject: Re: aliases not getting expanded inside functions?
Date: Sat, 11 Jan 2003 01:19:23 -0200	[thread overview]
Message-ID: <15903.36155.716460.639226@fisica.ufpr.br> (raw)
In-Reply-To: <1030106125404.ZM4660@candle.brasslantern.com>

Sorry I couldn't follow up earlier :-( Anyway the below told me how to
pass parameters by name to a function so that it changes the values.
Good!

Bart Schaefer (schaefer@brasslantern.com) wrote on 6 January 2003 12:54:
 >On Jan 6,  6:29am, Carlos Carvalho wrote:
 >}
 >} % a[1]=name1 a[2]=name2 etc.
 >} % b[1]=b_name1 b[2]=b_name2 etc.
 >} 
 >} and then to do the transfer
 >} 
 >} for ((i=1; i< number-of-elements; i++)) {
 >} 	: ${(P)b[i]::=$a[i]}
 >} }
 >
 >I presume you mean ${(P)${b[i]}::=${(P)${a[i]}}}

Yes, sorry, according to my example you're right. I just note that the
braces are not necessary in ${b[i]}, $b[i] works as well.

 >but I can't figure out
 >_why_ you'd want to do that.
 >
 >This sort of question often results from a sequence of events along the
 >lines of:  Problem X is encountered.  Solution Y is considered.  Attempt
 >to implement Y fails at detail Z.  The list is asked how to accomplish Z.
 >
 >Nearly as often, the right thing is instead to ask the list how to solve
 >problem X, because there's a better solution than Y.

Agreed, so here's the story, with two questions. I read a csv file
that comes from a spreadsheet and need to split the fields to
different variables. Instead of doing the full parsing of the data
line by hand, it's easier to have zsh do the split:

fields=( ${(s:;:)dataline} )

Now comes the first question: when there are several consecutive
semicolons the fields end up empty. This is correct, the problem is
that zsh removes the empty fields from the assignment, and instead of
getting 15 fields with many empty I have only 6 (I mean ${#fields} is
less than the number of variables in $dataline). Is there a way to
avoid this? I vaguely recall an option to not remove empty values from
the line but didn't find it. I've worked around the situation by
filling consecutive semicolons with some characters before doing the
split, but it's a hack.

Next, it's necessary to deal with the fields by meaningful names, so I'm
doing

rate=$fields[1] capital=$fields[2] etc.

I modify the variables directly, not only through fields. Later on I
have to copy all these fields to other variables like

rate_prev=$rate capital_prev=$capital etc.

Instead of copying manually I'd like to do

rate_prev=$fields_prev[1] capital_prev=$fields_prev[2] etc.

only once, and then just do fields_prev=( $fields ) whenever I have to
copy the values. This way with a single assignment all variables are
copied to the *_prev counterparts. If this is not possible, I
mentioned some variant of a loop like

for ((i=1; i<= num_fields; i++)) {
    fields_prev[i]=$fields[i]
}

which Bart said should be ${(P)${fields_prev[i]}::=${(P)${fields[i]}}}

However this doesn't work because I cannot assign to the individual
variables (ex. capital=$((capital+interest)) ) without losing the
connection with the fields array.

If you have any better ideas please speak up. As I said, I used the
trick above in another place to make a function change the value of a
parameter, so it's already been useful. Thanks for it.


  reply	other threads:[~2003-01-11 11:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 15:31 Carlos Carvalho
2003-01-03 15:39 ` Zefram
2003-01-03 15:45 ` Phil Pennock
2003-01-03 17:24   ` Carlos Carvalho
2003-01-03 17:44     ` Phil Pennock
2003-01-03 18:10       ` Carlos Carvalho
2003-01-03 18:54         ` Zefram
2003-01-06  8:29           ` Carlos Carvalho
2003-01-06 12:54             ` Bart Schaefer
2003-01-11  3:19               ` Carlos Carvalho [this message]
2003-01-11 18:40                 ` Bart Schaefer
2003-01-13 17:59                   ` Carlos Carvalho
2003-01-13 18:48                     ` Bart Schaefer
2003-01-13 21:40                       ` Carlos Carvalho
2003-01-14  5:10                         ` Bart Schaefer
2003-01-14 11:44                           ` Roman Neuhauser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15903.36155.716460.639226@fisica.ufpr.br \
    --to=carlos@fisica.ufpr.br \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).