All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: cilc: name space inconsistency
Date: Fri, 17 Oct 2014 15:15:49 +0200	[thread overview]
Message-ID: <20141017131548.GA1524@e145.network2> (raw)

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

I started rewriting my policy using name spaces again. I was assuming the the name space issues were fixed.

However I am encountering, what i believe, is an inconsistency.

The block statement is used to declare a name space

in module a i declare the a (root) name space

    (block a
        ...
    )

in module b i declare the b name space in the existing a (root) name space

    (in a
        (block b
            ...
        )
    )

All is well so far... However if i now want to declare the c name space in the existing a.b name space then cilc is unable to resolve the a.b name space

    (in a.b
        (block c
            ...
        )
    )

    "Unable to resolve a.b in in statement..."

The a.b name space exists

The workaround to this inconsistency is to create duplicate declarations:

    (in a
        (block b
            (block c
                ...
            )
        )
    )

Now the b name space is declared two times, but it works around the issue

Why can it not resolve the existing a.b name space?

-- 
Dominick Grift

[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]

             reply	other threads:[~2014-10-17 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 13:15 Dominick Grift [this message]
2014-10-20 13:34 ` cilc: name space inconsistency Dominick Grift

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=20141017131548.GA1524@e145.network2 \
    --to=dac.override@gmail.com \
    --cc=selinux@tycho.nsa.gov \
    /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.