these function are for checking for mixed inheritance. haven't

>>61677720

so...
this is the power of OO

File: Screen Shot 2017-08-01 at 12.32.28 PM.png (201KB, 1206x1094px) Image search: [Google]

201KB, 1206x1094px

>>61677747
doing it any other way would result in you creating the same information framework.

>>61677793
which is ironic I say that because I am actually creating an inheritance system using an OO language and approach.
The type checking is for different parsable chunk types. It's for a statistical parser... at least . I think

>>61677720
#include <stdio.h>
int main(void) {
printf("Hello world");
return 0;
}

this is for hello world.|

haven't even tested my code. and i know it works ...

are you this good?

>>61677720
wouldn't you avoid this problem by using class inheritance? also var _ = this is cringy.

>>61677720
use eslint faggot

>>61678661
I need mixed inheritence. parasble chunks can play different roles. they can be of different types. so i need all those potentials to be there.
those functions are just for checking if something inherits from something else.

>>61680130
provide an example

File: 1500407246412.jpg (778KB, 1700x956px) Image search: [Google]

778KB, 1700x956px

>>61677720
>>61677793
>var _ = this
>_.isChecking = x; x comes out of fucking nowhere
>var has = false; has isn't ever used
>mixed spacing inside ifs

also, i'm not sure about what checkedAlready is trying to avoid. i mean, it seems you're trying to cache the results to avoid wasting processing power, however _.checked is only updated when klass == _.isChecking, not when it's from a super class, and i'm sure an equals test is cheaper than traversing the _.checked array every single call.

probably i'm just being retarded, anyway.