This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/31645] New: Error on reading Byte Order Mark


We should probably take care of files that begin with a byte order mark (BOM;
see http://en.wikipedia.org/wiki/Byte_Order_Mark) because some editors (like
windows notepad) use them. We currently say:

$ xxd bom.f
0000000: fffe 2020 2020 2020 7072 696e 7420 2a2c  ..      print *,
0000010: 2022 4865 6c6c 6f20 776f 726c 6422 0a20   "Hello world". 
0000020: 2020 2020 2065 6e64                           end
$ gfortran bom.f 
bom.f:1.1:

\xFF\xFE      print *, "Hello world"                                          
1
Error: Non-numeric character in statement label at (1)
bom.f:1.2:

\xFF\xFE      print *, "Hello world"                                          
 1
Error: Invalid character in name at (1)


-- 
           Summary: Error on reading Byte Order Mark
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: fxcoudert at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31645


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]