Seeing as this is going to be a requirement for HoV, and Grue has promised to help out with save/load is needed, how about the File Functions documentation gets finished sometime soon? Stuff like 'you can't use FileSeekLine' if the file is opened in write mode, or verge will bomb' would be useful. And how you do write to a specific line without that would be nice too.

Zip

People certainly have /ignore zip.

Ah well, back to proper programming and compilers that give the right line number on error.

Zip

I actually just fixed a bug that would sometimes cause the vcerr() routine that performs reverse-lookups to crash rather than deliver the appropriate error message. Now, FileSeekLine on a write-mode file will return the error message written for it. But you are not intended to be able to FileSeekLine on a write-mode file. Note that verge doesnt do "read-write" file mode.. you're either reading or writing. Therefore seeking to an existing line doesnt really make sense. In general.. you're supposed to write the file in order. If you really want to be able to seek around inside a file while you're writing it, make it a binary file and use FileWriteString and such instead. FileSeekPos() will work in read or write mode. But to make FileSeekLine work on write mode would require the ability to append lines to the end of the file, and for write operations to - overwrite? insert? to existing lines... it would be messy. Using binary file functions will expect you to know what you're doing.

Newest exe is always here.

The line numbers are just randomly off, I think -- if there were any easy pattern to it, I'm sure it'd have been fixed by now. What I do is enter a blank line in the middle of the code and recompile, and if that increases the line reported for the error, I know the error is below the blank line. Then I delete it and add another blank line lower down, and so on, like that game where you guess a number and the person says if it's too high or too low.

I notice if I'm lazy with putting my {} in right I'm in for a world of pain = errors given in functions miles away, very little hint of where the problem is. But it's nothing like some of the variable nameing bugs I've had in c.

Thanks for the tips guys, this should speed things up - I was commenting the body of every function and seeing it let me put back in.

Zip

Don't know if this will help at all Vec, but it was odd so I thought I'd post it.
This code (unsurprisingly) give me a ';' expected error on line 144 (is infact line 127):

	SetRandSeed(fr_seed);


	fr_h1 += 360(;


	fr_h2 += 360;

Press enter after the rand seed line and save it gives error on line 145:

	SetRandSeed(fr_seed);





	fr_h1 += 360(;


	fr_h2 += 360;

But then, and this is the funky thing, if instead you press enter just before the fr_h1 and save it gives an error on line 146!:

	SetRandSeed(fr_seed);





	fr_h1 += 360(;


	fr_h2 += 360;

Now that looks identical to me, both here and in textpad, do din the difference and that'll probably help.

Zip