Skip to contentSkip to conversation

IDENTIFIER

DISCUSSION Brian May 2 participants 4 messages Jul 26, 2002 – Jul 28, 2002 SELinux security module

lore
Share & tools
lore

Brian May

author
#0 lore raw

Is it possible to relax the definition of IDENTIFIER:

{letter}({letter}|{digit}|_)* { return(IDENTIFIER); }

?

For the work I am doing, I need a way to seperate words and phrases seperately.

For instance dpkg_postinst/oav_update.

Any one symbol would be OK, but suggested ones include ~!@%&-=/

(or all of them, but I haven't considered if this will cause problems elsewhere; for instance : probably should not be used, it is used in allow statements).

Signature · 6 lines
Brian May <[email protected]>

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.
#1 lore raw
Quoted 5 lines · Brian May

Is it possible to relax the definition of IDENTIFIER:

{letter}({letter}|{digit}|_)* { return(IDENTIFIER); }

Any one symbol would be OK, but suggested ones include ~!@%&-=/

~ is already taken to mean a logical not.

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

author
#2 lore raw
Quoted 8 lines · Russell Coker
Quoted 5 lines · Brian May

Is it possible to relax the definition of IDENTIFIER:

{letter}({letter}|{digit}|_)* { return(IDENTIFIER); }

Any one symbol would be OK, but suggested ones include ~!@%&-=/

~ is already taken to mean a logical not.

Good point.

Better make that list: !@%&-=/

Signature · 6 lines
Brian May <[email protected]>

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.
author
#3 lore raw
Quoted 1 line · Brian May

Better make that list: !@%&-=/

Second thoughts: None of those characters can appear in M4 macro names, so maybe this isn't such a good idea...

In fact the current definition seems to be the same as the definition for M4 names.

Even if I just used this other character in type names, there is the risk that M4 will get confused and expand the wrong thing.

For now I will simply use the (perhaps more ugly looking) '__' instead.

Signature · 6 lines
Brian May <[email protected]>

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.