From: Grant Edwards <grante@visi.com>
To: Bart Veer <bartv@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Can't use expressions in ecos.ecc any more?
Date: Wed, 13 Dec 2000 07:33:00 -0000 [thread overview]
Message-ID: <20001213093606.A3094@visi.com> (raw)
In-Reply-To: <200012131523.eBDFNrm20122@sheesh.cambridge.redhat.com>
On Wed, Dec 13, 2000 at 03:23:54PM +0000, Bart Veer wrote:
>
> Grant> Didn't expressions in ecos.ecc used to work?
>
> Grant> $ ecosconfig tree
> Grant> C CYGNUM_MEMALLOC_FALLBACK_MALLOC_POOL_SIZE, Illegal current value 128*1024
> Grant> Legal values are: 32 to 0x7fffffff
>
> No. You can have expressions in the original CDL, but the code for
> reading back savefiles has never supported expressions.
>
> It is possible that a particular value is never referenced by other
> active CDL expressions. For example, if there were no constraints on
> CYGNUM_MEMALLOC_FALLBACK_MALLOC_POOL_SIZE then you could type in
> "128*1024", and in the generated header file you would end up with:
>
> #define CYGNUM_MEMALLOC_FALLBACK_MALLOC_POOL_SIZE 128*1024
>
> For much code this would just work.
That must have been what happened. I'd been using expressions
(just too lazy, I guess) for a couple things with 1.3.1, and
they generated errors with the CVS tree. It's certainly not
worth any extra effort to get it to work.
--
Grant Edwards
grante@visi.com
next parent reply other threads:[~2000-12-13 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001212140748.A15366@visi.com>
[not found] ` <200012131523.eBDFNrm20122@sheesh.cambridge.redhat.com>
2000-12-13 7:33 ` Grant Edwards [this message]
2000-12-13 7:38 ` Lewin A.R.W. Edwards
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=20001213093606.A3094@visi.com \
--to=grante@visi.com \
--cc=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
/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).