System Hash Categories

[Nestharus]

Because of its small size and global practicality, this was put into Mfn.

Please graveyard this, thank you ^_^.

 

[Romek]

I wonder if I'm the only one who finds this useless.
Very useless.

And the in-code credits for something as useless as this is overkill.

Your [hidden] tags are messed up.

library requiresHcn requires Hcn
endlibrary

 

[Nestharus]

I wonder if I'm the only one who finds this useless.
Very useless.

And the in-code credits for something as useless as this is overkill.

Your [hidden] tags are messed up.

library requiresHcn requires Hcn
endlibrary

Was created to save memory for maps using various systems. The reasoning behind this small library was in the description.

Also,

library requiresHcn requires Hcn
endlibrary

Follows Mfn conventions

 

[Tyrande_ma3x]

> I wonder if I'm the only one who finds this useless.
Nope, you're not alone.

 

[kingkingyyk3]

What is the uses of this?:nuts: I didn't see any goodies...

 

[Romek]

> Was created to save memory for maps using various systems.
I can't think of any systems that would need something like this. =|

> The reasoning behind this small library was in the description.
No it's not.

> Follows Mfn conventions
Which are?

So what's the point in the little library?

// Is there something against doing this?
library something requires Hcn
 // Some stuff
endlibrary

// Would you rather users do this?
library something requires requiresHcn
 // Some stuff
endlibrary

...

 

[Nestharus]

This is just a simple library... it's only useful so that things don't have to be re-declared over and over again. It just defines common category names.

I do use it for my stuff as it is convenient and it does save on memory, but that's fine. It only took me 2 minutes to make because I found that it would be better to use a library rather than have a set of the same variable names in 10 different systems.

 

[Romek]

Mind replying to everything else I've said?
Including the stuff about the credits being overkill.

 

[Trollvottel]

I actually find it useful. this way you would do things like

call Save......(ht, GetHandleId(<randomhandle>), X, .....)
call Save......(ht, GetHandleId(<randomhandle>), Y, .....)
call Save......(ht, GetHandleId(<randomhandle>), Z, .....)

which is a good idea imo.

 

[Nestharus]

Mind replying to everything else I've said?
Including the stuff about the credits being overkill.

sure, didn't see that stuff in the later post as I was probably posting my message as you were posting yours, lol. Look at the post times-

Today 02:46 AM
Romek

Today 02:46 AM
Nestharus

And the in-code credits for something as useless as this is overkill.

I believe that any resource should be allowed the opportunity to get credits in the map that uses it, thus for any resource that I make I always use Mfn's built credit function (ugly, but I don't want to build more credits than I have to with the Mfn credit building macro).

> Was created to save memory for maps using various systems.
I can't think of any systems that would need something like this. =|

I can. Any system that uses a hash table and stores native types (not structs or w/e, so no need for custom categories) can use this. Any framework that does that can use this : ). A system I'm working on right now, Spawn, uses this.

> The reasoning behind this small library was in the description.
No it's not.

so everything within a map doesn't have to define hash table categories over and over again from thingie to thingie.

> Follows Mfn conventions
Which are?

In the Mfn documentation under Designer Conventions (some of that page isn't current)

So what's the point in the little library?
Jass:

// Is there something against doing this?
library something requires Hcn
// Some stuff
endlibrary

// Would you rather users do this?
library something requires requiresHcn
// Some stuff
endlibrary

...

Fully described in Mfn conventions. A very brief description is that it allows libraries, utilities, systems, and frameworks to require other libraries, utilities, systems, and frameworks very easily. Some of them might have a lot of parts (Ftmn, being re-written) has 5 or 6 I think. The requiresThingie requires all parts of the library, utility, system, or framework so that the using thingie can just require the requiresThingie and not have to do like requireThisThingie, requireThatThingie, requireMainThingie, etc, etc ; D.