HomeUser Control Panel (unavailable in archive)ForumsTutorialsArt GalleryResourcesMaps

deprecation?

02-28-2009, 09:40 PM#1
Vexorian
I think I have to deprecate nested scopes for everyone's well being. Does anybody have strong reasons for me not to deprecate them? Does anyone actually use them?
02-28-2009, 09:57 PM#2
Skater
i use them sometimes.
and do you mean only scopes in scopes or also scopes in libraries?
02-28-2009, 09:58 PM#3
TriggerHappy
I never use them.
02-28-2009, 10:05 PM#4
C2H3NaO2

I think they are very useful in textmacros, that represent data structures.
I also use them sometimes to structure code.

I would suggest to extend them, with new access modifiers to make thinks only access able to the parent scope/library.
02-28-2009, 10:59 PM#5
Vexorian
A library is a scope , so nesting scopes inside a library would be banned as well.
02-28-2009, 11:02 PM#6
Flame_Phoenix
Having nested scopes as an extra functionality will only benefit advanced users. As for beginners, don't expect much from them.
It is mainly your choice, is vJASS directed do a newbie population? Or to people with high level of knowledge? Do you want it to be used by all groups?

Personally, I don't think you should remove them. They can still be useful for some people in some cases and removing them would harm those people, one way or another.

You can however "upgrade" or make some sort of improvement if you find necessary.

Just my opinion... hoping it helps.
02-28-2009, 11:19 PM#7
MaD[Lion]
i use struct and libraries only so if i want something wrapped in something i use like

WrapperStruct.Something()

anyway it would be nice to have nestex static struct or something, like for java.

so u can do like:

StructA.StructB.MethodForB() //static, just to keep things organized
02-28-2009, 11:33 PM#8
Vexorian
Quote:
Originally Posted by C2H3NaO2

I think they are very useful in textmacros, that represent data structures.
I also use them sometimes to structure code.

I would suggest to extend them, with new access modifiers to make thinks only access able to the parent scope/library.
If you think about it, all legit uses for nested scopes are pwned terribly by a struct full of static stuff, aren't they?
03-01-2009, 02:15 AM#9
Jazradel
I use nested structs for naming stuff sometimes.
03-01-2009, 02:24 AM#10
darkwulfv
I never understood the point of doubling scopes, so it wouldn't bother me in the least.
03-01-2009, 02:58 AM#11
xombie
Wouldn't a struct inside of a scope then qualify as a nested scope? In which case please do not remove it.

Also, did anybody else's font change? Rather than the usual MS Reference Sans that is used on this site for some reason its all in Arial now.
03-01-2009, 03:17 AM#12
darkwulfv
I too have noticed that. I thought maybe it was my computer, but...
03-01-2009, 03:22 AM#13
TriggerHappy
Quote:
Originally Posted by darkwulfv
I too have noticed that. I thought maybe it was my computer, but...

Nope, me too.

Sorry to get off topic.
03-01-2009, 08:42 AM#14
C2H3NaO2
Quote:
Originally Posted by Vexorian
If you think about it, all legit uses for nested scopes are pwned terribly by a struct full of static stuff, aren't they?
I was talking about things like that:
Expand JASS:
(Ok its old and not really good ^^; just for example)
Of cause it would be possible to put all this as static members and static methods into a struct. But in my opinion that would be ugly and stupid (like java).
The only problem for this is, that it can be accessed from everywhere. Here would a new new access modifier be useful.

Or if I have a huge library (in size of caster system) i could put some stuff into nested scopes to avoid name conflicts and bring more structure to it. (Yes here we can use the ugly and stupid thing with putting it all as static stuff in a struct again)

edit: the highlighter doesn't seams to highlight "not"
03-01-2009, 09:06 AM#15
Troll-Brain
Inside a private hudge code (a scope or a library) i use sometimes nested scopes for the readability of the code (hide/undide scopes).
Plz don't deprecated this.