From: Richard Earnshaw <rearnsha@armltd.co.uk>
To: gas2@cygnus.com
Cc: richard.earnshaw@armltd.co.uk
Subject: Problems with gasp
Date: Sat, 18 Feb 1995 08:17:00 -0000 [thread overview]
Message-ID: <9502181619.AA19012@sun52.armltd> (raw)
I'm having some dificulty with variable expansion in gasp. I'd like to concatenate
a variable with an additional string and put it back in the same variable. The
code I have is, essentially:
Temp .ASSIGNC "string"
...
Temp .ASSIGNC "\&Temp'extra"
but the result of this is the string \&Temp'extra, not "stringextra" as desired.
This does not happen if I concatenate a macro parameter with extra, eg
.MACRO Foo Temp
bar .ASSIGNC "\Temp'foo"
.ENDM
Foo xxx
gives "xxxfoo" as desired.
Is this not inconsitent?
Additionally, here's a patch for istrue() in gasp.c, for strings NE never returns
true.
*** gasp.c~ Thu Jan 19 21:04:07 1995
--- gasp.c Sat Feb 18 16:04:40 1995
***************
*** 2330,2336 ****
res = 0;
}
else
! res = cond == EQ && same;
}
else
/* This is a numeric expression */
--- 2330,2336 ----
res = 0;
}
else
! res = cond != EQ ^ same;
}
else
/* This is a numeric expression */
reply other threads:[~1995-02-18 8:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9502181619.AA19012@sun52.armltd \
--to=rearnsha@armltd.co.uk \
--cc=gas2@cygnus.com \
--cc=richard.earnshaw@armltd.co.uk \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).