From: James Carter <jwcart2@tycho.nsa.gov>
To: Steve Lawrence <slawrence@tresys.com>,
Dominick Grift <dominick.grift@gmail.com>
Cc: selinux <selinux@tycho.nsa.gov>
Subject: Re: secilc: in statement ordering limitations
Date: Tue, 27 May 2014 12:47:23 -0400 [thread overview]
Message-ID: <5384C19B.7040001@tycho.nsa.gov> (raw)
In-Reply-To: <537F6395.6000002@tresys.com>
On 05/23/2014 11:04 AM, Steve Lawrence wrote:
> On 05/23/2014 10:32 AM, Dominick Grift wrote:
>> On Fri, 2014-05-23 at 09:15 -0400, James Carter wrote:
>>
>>> Could you give me a little bit more information on what you are doing?
>>
>> Strange.. It is kind of hard for me to put it any other way.
>>
>> I have a short 5 minute video that demo's the issue:
>>
>> https://www.youtube.com/watch?v=hU_yVZJpAyM
>>
>> If you are not able to view the demo then i guess i will have to find
>> another way to explain it
>>
>
> I think this is an example of the core problem:
>
> (in foo.bar
> (type x))
>
> (in foo
> (block bar))
>
> (block foo)
>
> So, an in-statement is inserting into a block that is created by another
> in-statement, so there's an order dependence.
>
So to fix this we need to split up the processing for "in", so that blocks and
macros are processed first?
Jim
--
James Carter <jwcart2@tycho.nsa.gov>
National Security Agency
prev parent reply other threads:[~2014-05-27 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 16:30 secilc: in statement ordering limitations Dominick Grift
2014-05-21 18:41 ` James Carter
2014-05-23 13:15 ` James Carter
2014-05-23 14:32 ` Dominick Grift
2014-05-23 15:02 ` Dominick Grift
2014-05-23 15:04 ` Steve Lawrence
2014-05-27 16:47 ` James Carter [this message]
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=5384C19B.7040001@tycho.nsa.gov \
--to=jwcart2@tycho.nsa.gov \
--cc=dominick.grift@gmail.com \
--cc=selinux@tycho.nsa.gov \
--cc=slawrence@tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.