What year is this?tido wrote:ACTUALLY...
*.conf DOES use ONE WHOLE EXTRA BYTE of RESOURCES because of the extra letter (*.cfg has only three). So technically, it will take a few more CPU cycles to parse that string.
Also, I'm pretty sure it will use some more cycles looking the file up on the drive.
.conf /.cfg?
Forum rules
Before you make a thread asking for help, read this.
Before you make a thread asking for help, read this.
Re: .conf /.cfg?
Now posting IN STEREO (where available)
Re: .conf /.cfg?
It still counts goddamnit!!mike wrote:What year is this?
Who is online
Users browsing this forum: No registered users and 3 guests