• Post Reply Bookmark Topic Watch Topic
  • New Topic

never seen it before  RSS feed

 
miguel lisboa
Ranch Hand
Posts: 1281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
pls have a look at this:

i was compiling an innocent class when this happens; later i deleted the line, tried to reproduce the outcome but eversince compiled ok; google didnt help
line 17:
 
Srinivasa Raghavan
Ranch Hand
Posts: 1228
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Normally when you open any files created in unix flavours, in windows environment some binary characters are appended at EOL. Try to open this java file in a text editor like edit plus or even text pad and check whether any binary characters are there.
 
miguel lisboa
Ranch Hand
Posts: 1281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i'm with TextPad and winXp; also, i cant reproduce it anymore

what's eol?

thanks for answering!
[ March 28, 2005: Message edited by: miguel lisboa ]
 
Srinivasa Raghavan
Ranch Hand
Posts: 1228
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm sorry, EOL is End of Line.
May be that line would have got any special character that produced this error.
 
Arun Prasath
Ranch Hand
Posts: 192
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
EOL - End of Line.
Try changing the Editor from Textpad to something else.
 
Marilyn de Queiroz
Sheriff
Posts: 9082
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
eol = end of line

I would try to open the offending file in a hex editor if it happens again. TextPad is one editor where you can view the file in a hex format.
 
Ernest Friedman-Hill
author and iconoclast
Sheriff
Posts: 24217
38
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
EOL is "end of line", and he's got it backwards; it's Windows files that have the extra characters in them.

In any case, ASCII 7 is the "BEL" (beep) character; you can type one with "Control-G". This character, of course, has nothing to do with Windows/UNIX issues. Depending on what editor you use, you may find it more or less easy to accidentally insert a control character. If it just happens this once, forget about it. If you find it's happening consistently, I'd first read my editor's documentation to find out what key strokes might have caused this to happen.
 
miguel lisboa
Ranch Hand
Posts: 1281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks to everyone for posting the answers!

as i said, now the file compiles and runs ok;

the only thing i can remember of is that i'm using an old 3 beta version of AutoIt; later someone in TextPad or AutoIt forums (i cant remember) wrote a script that creates an extra line when pressing enter; anyway i use it for a long time and it never generated any kind of weird behaviour.
 
miguel lisboa
Ranch Hand
Posts: 1281
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
@Ernest Friedman-Hill

here's your beep:


i'm working with a new keyboard, so probably i made some kind of unintended (and unvisibe) kind o beep

 
David Harkness
Ranch Hand
Posts: 1646
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Most decent editors also have a "show (in)visibles" option that will show you any invisible characters. In mine (CodeWright), it shows spaces as periods, tabs as a -> char, etc.

You could turn this on and then try various control-key combinations to see if one actually inserts that character.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!