If GJS calls them something, I'd like to call them the same.
Name:
Anonymous2007-09-29 14:52 ID:59I37K84
Members if they're accessed directly, like a struct's. Attributes if you need to call accessors (or go through the C# attribute mechanism), and properties if the accessors compute the value rather than returning it straight from somewhere.
Depends on circumstance really. In CORBA there's no point in calling them anything except attributes.
In C though, structs and unions have fields, like a fill-out form would have.
Name:
Anonymous2007-09-29 16:06 ID:cndnQ8y5
>>13
This is why I think OO advocates are faggots, even though I use OO all the time.
It's a simple fucking idea. Pick one word and stick to it. If you feel the need to differentiate on minute details, go back to C++.
Name:
Anonymous2007-09-29 16:31 ID:59I37K84
>>14
Yeah, I rarely use C++ or stuff like that anymore. It's C and Haskell on my own stuff, and Perl & Java at work. But in general it's useful to have definitions for stuff besides the "it's like a variable that you get to with the deref operator" thing everyone knows informally, inside their head.
I mean, this is still quite a way from full-blown design pattern faggotry.
Name:
Anonymous2007-09-29 17:21 ID:ZxIUcCsi
>>14
Case in point:
static_cast
const_cast
dynamic_cast
reinterpret_cast
IT IS A FUCKING CAST.
Name:
Anonymous2007-09-29 17:25 ID:tT5SS3h5
>>14
I think like this man. And I just call them properties.
Fire, earth, wind and water. These are the elements that all objects are built from. You call them by speaking their true names. To keep it easy, they are all named cdr.
Name:
Anonymous2007-09-29 21:48 ID:cndnQ8y5
Well, to be fair, we programmers have to put up with a lot of bullshit like this, not just in the OO world (although OO is far and away the worst of the lot).
For example, how many different names are there for hashes? I can think of four (or five if you include tables) off the top of my head. What the fuck?
You people are silly. Associative arrays, maps, multimaps and so forth are just names for the interface. The usual C++ STL, for instance, implements maps, multimaps, sets and multisets on top of red-black trees; that's why in order to use something as a key in a map or a member in a set it needs to have the ordering operators defined.
A hash map, then, is just a map implemented as a hash table.
All of these expressions have meanings, and you would do well not to lump them together so that you can forget all but one of them.
Name:
Anonymous2009-03-06 10:03
Have to provide a way to check When someone has DONE IT SO are vi m and Emacs and was looking for any reason to use a concatenative language Forth Joy.