Teeworlds - development

oy

[teeworlds/teeworlds] Pull request closed: #2675 Fix rand init error message

12:25

oy

[teeworlds:master] 2 new commits

01b9de8 Fix rand init error message - ChillerDragon 208d8c7 Merge pull request #2675 from ChillerDragon/pr_... - oy

oy

[teeworlds:master] 2 new commits

101b7b3 fixed line breaks - oy 293209e do a proper bounds check for types when unpacki... - oy

15:57

oy

[teeworlds/teeworlds] Issue closed: #2649 Access outside buffer

oy

[teeworlds/teeworlds] Pull request closed: #2478 fix #541 : remove weak hook using

16:31

oy

[teeworlds:master] 6 new commits

d03c1f2 mitigate weak hook - nheir 241f62c ignore dragging force when firing ninja - nheir 25e9ce4 move drag velocity to CCharacter::TickDiffered - nheir 6cefadb comment drag velocity - nheir 1894f14 fix: use drag velocity on client side - nheir

16:31

oy

[teeworlds/teeworlds] Issue closed: #541 Different hook strength

16:31

oy

[teeworlds/teeworlds] Pull request closed: #2148 Remove "weak" hook

Is there any guidelines for modding or any overview of internal TW architecture or docs exists?

Learath2 had this

19:46

19:46

or someone from ddnet party xd

That's hardly useful it's just the relationships between the classes

19:54

There are no guidelines no docs. We all just wing it

19:55

For vanilla there is "Don't use STL"

hm, why

Well in the past the reason was the way matricks managed the memory

20:44

But since mem_alloc is now just malloc, it's there for performance concerns I guess

20:44

Though I'm sure a std::vector<T> implementation from any respectable vendor performs better than our array<>

Even array<> isn't used that often. There are several places with linked lists, sometimes allocated from CHeap. Dynamic allocations are just avoided in general

Linked lists can perform comparably the way we use them (inside preallocated chunks and intrusively) but most of the time array<> and vector<> will handily outperform them because of cache hits and prefetch

True

The hashmap implementation we have for the serverbrowser is not even close to optimal either

Most of these list were introduced before array<> I think