where to find FRIK_FILE
Moderator: InsideQC Admins
7 posts
• Page 1 of 1
where to find FRIK_FILE
I keep hearing about FRIK_FILE. Where can one obtain a copy of it?
- MonkRocker
- Posts: 6
- Joined: Sat Aug 07, 2010 5:06 pm
FRIK_FILE is one of many QuakeC extensions that a number of engines (FTEQW, Darkplaces, etc.) supports.
I know FrikaC made a cgi-bin version of the quakec interpreter once and wrote part of his website in QuakeC
(LordHavoc)
-

frag.machine - Posts: 2090
- Joined: Sat Nov 25, 2006 1:49 pm
frag.machine wrote:FRIK_FILE is one of many QuakeC extensions that a number of engines (FTEQW, Darkplaces, etc.) supports.
Right but is there a src file or a function list somewhere?
- MonkRocker
- Posts: 6
- Joined: Sat Aug 07, 2010 5:06 pm
MonkRocker wrote:frag.machine wrote:FRIK_FILE is one of many QuakeC extensions that a number of engines (FTEQW, Darkplaces, etc.) supports.
Right but is there a src file or a function list somewhere?
You may start here:
http://dpwiki.slipgateconstruct.com/ind ... Extensions
I know FrikaC made a cgi-bin version of the quakec interpreter once and wrote part of his website in QuakeC
(LordHavoc)
-

frag.machine - Posts: 2090
- Joined: Sat Nov 25, 2006 1:49 pm
frag.machine wrote:MonkRocker wrote:frag.machine wrote:FRIK_FILE is one of many QuakeC extensions that a number of engines (FTEQW, Darkplaces, etc.) supports.
Right but is there a src file or a function list somewhere?
You may start here:
http://dpwiki.slipgateconstruct.com/ind ... Extensions
Awesome. Thanks. And one more thing, I keep seeing functions declared like this:
- Code: Select all
float(string s) stof = #81;
What does the #81 part mean?
- MonkRocker
- Posts: 6
- Joined: Sat Aug 07, 2010 5:06 pm
it means builtin number 81.
or in other words, this function is provided by the engine, I'm going to call it stof in my code, but the engine knows it only by the name '81'.
The engine provides functionality almost purely based upon numbers. It can check the number of arguments passed to it (see centerprint) but that's usually only for string concatination, and only for a handful of them.
Put another way, you can change #81 to #424212 if you want, but it'll crash when you run it - its a magic number, all that matters is that it matches the behaviour.
(you are free to change the name of your builtin definition without any issues. you can do this to wrap it easily. but if you change the # you will crash and burn, unless you comply with the required behaviour of the new number, they're magic, okay?).
or in other words, this function is provided by the engine, I'm going to call it stof in my code, but the engine knows it only by the name '81'.
The engine provides functionality almost purely based upon numbers. It can check the number of arguments passed to it (see centerprint) but that's usually only for string concatination, and only for a handful of them.
Put another way, you can change #81 to #424212 if you want, but it'll crash when you run it - its a magic number, all that matters is that it matches the behaviour.
(you are free to change the name of your builtin definition without any issues. you can do this to wrap it easily. but if you change the # you will crash and burn, unless you comply with the required behaviour of the new number, they're magic, okay?).
- Spike
- Posts: 2892
- Joined: Fri Nov 05, 2004 3:12 am
- Location: UK
7 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest
