OFPLint V1.20 final

[Planck]

Hmmmmm......maybe p3d's in the data3d are exempt.

I'm almost positive that it doesn't work for user made addons........but I might be wrong.  


Planck

[Mikero]

Hmmmmm......maybe p3d's in the data3d are exempt.

>a strange file.p3d

odd one isn't it!

I assumed like you that quotes were necessary. They are not. nor are they needed for the resistance stuff \o\blah\blib. O.pbo being an addon like any other, all addons are exempt as well

Another wrinkle is :

model = \data3d\a file somewhere.p3d;

can be defaulted to

model = a file somewhere;

p3d is always assumed by default (for models) and data3d is the assumed directory

Personally, I think it's bad practice and a bad habit NOT to have spaced filenames in quotes, but the engine allows it. And, the intent of me mentioning it at all was to point out the often liberal and over-use of quoting things when they do nothing (except slow the parsing down a little)

[Planck]

Well I knew that if you didn't specify the pbo in the path that data3d was assumed.

However, I have come across cases where the path would not work if there were spaces in the p3d file name and the only way I found to get it working was to change spaces to '_' or remove them altogether.

I do know that some of BIS's p3d's in the data3d.pbo have spaces in their names though.....I have no clue other than the thought that data3d is exempt in some way from that restriction.


Planck

[Mikero]

>I have come across cases where the path would not work if there were spaces in the p3d file

from memory, there is an issue with filenames in the mission.sqm or the description.ext (forget which), when selecting the mission.island (eg Big Fred.cain).

all in all, it's just plain bad practice not to quote spaced anything.

anyway, please test this thing for me Mr Planck.

[Mikero]

Version 1.20, the final, is on first page. It includes a BINARISE (cpp2bin) function and FULL SOURCE code.

[i.Q]

thanks !