Project

General

Profile

Actions
Copy link

Bug #141

closed

Reserved names cannot be used for aliases or interfaces

Added by Chris Buechler about 15 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
2.0
Start date:
11/08/2009
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

If a reserved name, such as 'max', is used for an alias or interface it breaks the ruleset. Need either an alias blacklist, or to append something automatically to alias names in the ruleset.

Actions
Copy link
 #1

Updated by Scott Ullrich almost 15 years ago

  • Status changed from New to Feedback
Actions
Copy link
 #2

Updated by Chris Buechler almost 15 years ago

  • Status changed from Feedback to New

no change.

Actions
Copy link
 #3

Updated by Scott Ullrich almost 15 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Ermal Luçi almost 15 years ago

It would be better to just add a single char to the beginning of alias names.
So people can have some freedom on name choosing.

Actions
Copy link
 #5

Updated by David Miller over 13 years ago

I know this bug is marked as complete but I just ran into this problem using the alias name of "all". With a 2.0 RC1 build from March 16th.

Actions
Copy link

Also available in: Atom PDF