|
Ah, the famous Tupleware! It keeps the fridge organized. Just remember to manually execute the garbage collection after a while 
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Exactly. I bet there will be web2.0 tupperwares in a few years, that could communicate with your fridge.
|
|
|
|
|
If you don't remove the leftovers for a few years they would have established some pimitive form of government, like democracy.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
And then, they would establish voting in the Lounge.
|
|
|
|
|
It's like a struct without defining it. It's useful because you can avoid having to make up names for things 
|
|
|
|
|
Uhm, if there is a collection of data passed around it better should have a name, at least to mark its purpose. Being able to create unnamed objects at will means lowering the expected amount of design involved in writing solutions.
Unnamed entities (may them be structures or functions or whatever) may be a very good instrument but like a plasma torch they shouldn't be used carelessly...
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
harold aptroot wrote: you can avoid having to make up names for things
Exactly why I regretted using one about five minutes after I used one 
It's also my biggest problem with functional languages, what the hell do you have in your tuples!? (int, int) isn't telling me much... 
The only time a tuple did me any good was when my boss made fun of me for not having a formal education in IT.
He said something, I asked him "what's that?", and he was all like "haha, yeah you didn't get that in school, of course."
I was their top programmer at the time, and I think that bothered him as, indeed, unlike my coworkers I didn't have formal education.
So anyway, I did some Open University courses and I read about tuples.
In a next conversation with my boss I told him "it's just some tuple" and then he asked me "what's that?"... THAT'S PAYBACK TIME BIATCH!!!
|
|
|
|
|
Tuples are pointless in their current implementation. The size limit is completely arbitrary, and the work around for the size limit is absurd. You'd be better off with a static class that contains a List<object> property. At least that way, you could populate it with a virtually unlimited number of data items, of any type.
Of course, it doesn't have to be static, so if you want persistence, or a unique ObjTuple for given situations, it's easy to code it as needed. I provided the IsString methods to illustrate type-checking that you might want/need. It could be expanded to include all intrinsic types.
public static class ObjTuple
{
public static List<object> Objects { get; set; }
<pre>
public static void Create(params object[] parameters)
{
ObjTuple.Objects = (ObjTuple.Objects == null) ? new List<object>() : ObjTuple.Objects;
ObjTuple.Objects.Clear();
ObjTuple.Objects.AddRange(parameters);
}
private static bool InRange(int index)
{
return (index >= 0 && index < ObjTuple.Objects.Count);
}
public static bool IsString(int index)
{
return (ObjTuple.InRange(index) && ObjTuple.IsString(ObjTuple.Objects[index]));
}
public static bool IsString(object obj)
{
return (obj is string);
}
}</pre>
Usage would be something like this:
ObjTuple.Create("Test", 1, 5.1);
foreach(object obj in ObjTuple.Objects)
{
if (ObjTuple.IsString(obj))
{
}
}
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 26-Aug-16 7:58am.
|
|
|
|
|
Let's just hope you never have two threads trying to use that class at the same time.
And that you never need to call two methods that use it (or one method in a loop) and use the return value of both in the calling method.
And don't even think about using it in ASP.NET!
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: And don't even think about using it in ASP.NET!
Everything you listed can be easily addressed, except ASP.NET. Nothing can fix that, because it's a web technology.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Angular 2 seems set to fix it, based on my recent self-tuition in that framework and the TypeScript language, which it is written in.
Do what thou wilt shall be the whole of the Law. - Liber AL vel Legis 1:40, Aleister Crowley
|
|
|
|
|
Seems a bit of overkill when you could just return List<object>. But hey that's just me.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
A typed list, how pretensious, even if the type is object. In my appy days we used ArrayList.
Do what thou wilt shall be the whole of the Law. - Liber AL vel Legis 1:40, Aleister Crowley
|
|
|
|
|
LOL. Yessss, yessss, My Pretentious....
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Users of List<object> will pay a high price for the possible boxing/unboxing, or casting, or object Type inspection, that will occur ... or that will be necessary ... depending on the Types involved. And, the "opacity" of such code, like the current Item1 ... Item# syntax of .NET Tuples will, imho, make future code maintenance difficult.
Isn't this equivalent to using the old 'ArrayList structure ?
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|
|
Just keep in mind that in .Net a Tuple is a reference type (class), not a struct.
|
|
|
|
|
In C# 7, the new Tuple, is a struct.
Do what thou wilt shall be the whole of the Law. - Liber AL vel Legis 1:40, Aleister Crowley
|
|
|
|
|
Well, that opens up fur some confusion.
Why don't they just call them anonymous return types instead?
|
|
|
|
|
Jörgen Andersson wrote: a reference type (class), not a struct.
And, that's one reason I have avoided them: [^].
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|
|
Yes, I've read that. But that's a specific case.
If you read here[^] you'll find some performance comparisons.
You quickly realize that if you create, use and throw away, it makes sense to use a value type. But if your types are used more than once or twice before being destroyed, it makes sense to use reference types.
|
|
|
|
|
12334 3556 748 970 (5, 4, 3, 3)
Hint 1: The Doctor's order?
Hint 2: How many times do I have to tell you? I do not like them!
Hint 3: All this puzzling is taking time,
So let's resolve it with a rhyme.
The answer's there if you'll just look
At the cover of a children's book!
|
|
|
|
|
Trees eddy she ask
Edit: actually that guess doesn't fit!
|
|
|
|
|
4b 3w
That's quite a start on the black front!
|
|
|
|
|
Not sure it helps me* much though.
*I still don't have a clue.
|
|
|
|
|
CHEEK EAAR AKS DAN
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
