Opened 16 years ago
Last modified 16 years ago
#201 new defect
Boost Jam on Windows not handling 0x0d line endings correctly.
| Reported by: | Owned by: | somebody | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | component1 | Version: | 2.0 |
| Keywords: | bjam Boost Jam line-ending | Cc: |
Description
Boost Jam on Windows does not treat Unix style line endings (0x0d instead of 0x0d/0x0a) correctly. If it encounters a comment line, that comment will span multiple 'lines' until reaching a Windows line ending.
This should be changed so it does not matter whether the line ending style used is Windows or Unix or even if it changes from one line to the other.
Change History (1)
comment:1 by , 16 years ago
| Milestone: | M13 |
|---|---|
| Summary: | Boost Jam on Windows not handling Unix line endings correctly. → Boost Jam on Windows not handling 0x0d line endings correctly. |
Note:
See TracTickets
for help on using tickets.
Heh... I knew there was something bugging me about this report and I just realized what. Unix style line-endings are 0x0a and not 0x0d.
Unix style line endings are handled correctly by bjam and the only one that are not are old MacOS style ones 0x0d and I am not sure whether that is worth the effort to fix this.
The code implementing this end-of-line detection is the yylex() function in Boost Jam's scan.c module.