[Dr. Kylstein]

Maybe I'm the only one that cares, but the new "whitespace" characters don't work with setplayer or definesound.

[TerminX]

I'll have to look into that. You probably are the only one that cares, you're certainly the only one to even notice (or at least mention) that CONs can even be written with that syntax now.

[Hendricks266]

I saw that revision.

[Dr. Kylstein]

in 1524:

onevent (EVENT_DISPLAYSBAR) {

	setvar(RETURN, -1);

	rotatesprite(0, 178, 65536, 0, 1381, 0, 0, 24, windowx1, windowy1, windowx2, windowy2);

	rotatesprite(0, 0, 65536, 0, 1380, 0, 0, 24, windowx1, windowy1, windowx2, windowy2);

} endevent;

Quote

EDUKE.CON: In event `':
EDUKE.CON:117: error: symbol `0' is not a game variable.
EDUKE.CON:117: error: symbol `178' is not a game variable.
EDUKE.CON:117: error: symbol `65536' is not a game variable.
EDUKE.CON:117: error: symbol `0' is not a game variable.
EDUKE.CON:117: error: symbol `1381' is not a game variable.
EDUKE.CON:117: error: symbol `0' is not a game variable.
EDUKE.CON:117: error: symbol `0' is not a game variable.
EDUKE.CON:117: error: symbol `24' is not a game variable.
EDUKE.CON:118: error: symbol `0' is not a game variable.
EDUKE.CON:118: error: symbol `0' is not a game variable.
EDUKE.CON:118: error: symbol `65536' is not a game variable.
EDUKE.CON:118: error: symbol `0' is not a game variable.
EDUKE.CON:118: error: symbol `1380' is not a game variable.
EDUKE.CON:118: error: symbol `0' is not a game variable.
EDUKE.CON:118: error: symbol `0' is not a game variable.
EDUKE.CON:118: error: symbol `24' is not a game variable.

[Dr. Kylstein]

`definesound` is still being cantankerous about tabs. Consistently, it includes a tab immediately after the filename as part of the filename. It also screws up on some entries saying that "`' is a keyword" and "parameter define is undefined" on the line afterwards. Here's a pair that does that:

define	SQUISHED		69	definesound	SQUISHED		SQUISH1.VOC	-128  0   3   0   0

define	DUKE_JETPACK_OFF	51	definesound	DUKE_JETPACK_OFF   	JETPAKOF.VOC	  0   0   2   0   0

The first line causes it, the next line gets the error.

(r1528)

[The Commander]

I got this same problem when I added a few new sounds, I couldn't tell what the hell was wrong with it so I removed all the lines I added and started over again...

[Dr. Kylstein]

Another one: any line ending in a parenthesis or semicolon will make the parser interpret a comment on the next line.

	andvar(a, 2047);
	// we make sure the normal faces inward by comparing it to the actor's position within the sector

Quote

EDUKE.CON:23: error: expected a keyword but found `//'.
EDUKE.CON:23: error: expected a keyword but found `we'.
EDUKE.CON:23: error: expected a keyword but found `make'.
EDUKE.CON:23: error: expected a keyword but found `sure'.
[...]

My file had 64 errors, all caused by this.
Also, it keeps crashing while I'm reading the messages panel.
(r1539)

Edit:
rotatepoint doesn't play nice either, I had to remove commas and parentheses.

[Fox]

Obviuou if the CON is trying to read a comment tag (// or */) you missed some keyword, for example "addvar MYVAR // comment"

[TerminX]

Just post a CON file that causes as many different errors that it shouldn't as it can and I'll fix them all at once.

[Dr. Kylstein]

This attachment summarizes the entire thread:  EDUKE.CON (497bytes)
Number of downloads: 238 Have fun.

[TerminX]

Should be fixed in r1545.

[Dr. Kylstein]

I just discovered that definesound includes a trailing comma in the filename, but wrapping the filename in quotes seems to fix it. Everything else works so far. Thanks!

[TerminX]

Yes, that's correct. Commas are valid parts of filenames and support for using quotes in sound definitions was added specifically to address this.