| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0009078 | KWStyle | public | 2009-05-28 13:56 | 2009-05-28 13:56 | |||||||||
| Reporter | Tom Vercauteren | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||||||
| Status | new | Resolution | open | ||||||||||
| Platform | OS | OS Version | |||||||||||
| Summary | 0009078: More flexible IfNDefDefine rules - feature request | ||||||||||||
| Description | It would be great if one could specify more complex IfNDefDefine rules. Currently, it is only possible to use a mixture of the filename without extension, the extension and some given fixed characters. I would like to be able to specify for example: - if the file name and file extension should be transformed to uppercase before being matched - if the file name and file extension matching should be done in a case insensitive manner - use the "full" path in the include guard - use some regular expression | ||||||||||||
| Additional Information | For example, FooEngine/projBarWheel.hxx could be mapped to FOO_ENGINE_PROJ_BARWHEEL_HXX_ | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Attached Files | |||||||||||||
| Relationships | |
| Relationships |
| Notes | |
| There are no notes attached to this issue. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2009-05-28 13:56 | Tom Vercauteren | New Issue | |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |