Opened 14 years ago
Closed 14 years ago
#2648 closed Bugs (fixed)
Re-registering an existing suffix for a type fails erroneously, patch attached
Reported by: | anonymous | Owned by: | Vladimir Prus |
---|---|---|---|
Milestone: | To Be Determined | Component: | build |
Version: | Boost Development Trunk | Severity: | Problem |
Keywords: | type suffixes | Cc: |
Description
I've attached a patch against the development trunk that indicates what I believe is a problem in tools/build/v2/build/type.jam
.
The comments and the code suggest that re-registering a suffix to a type should be okay. I've included a snippet from the current trunk below.
# Specifies that files with suffix from 'suffixes' be recognized as targets of # type 'type'. Issues an error if a different type is already specified for any # of the suffixes. # rule register-suffixes ( suffixes + : type ) { for local s in $(suffixes) { if ! $(.type.$(s)) { .type.$(s) = $(type) ; } else if $(.type.$(s)) != type { errors.error Attempting to specify multiple types for suffix \"$(s)\" : "Old type $(.type.$(s)), New type $(type)" ; } } }
Attachments (1)
Change History (3)
by , 14 years ago
Attachment: | type.jam.patch added |
---|
comment:1 by , 14 years ago
Summary: | Re-registering an existing suffix for a type fails erroneously → Re-registering an existing suffix for a type fails erroneously, patch attached |
---|
comment:2 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
patch against development trunk