Thought about programming
-
Yup, sounds good. Only would need it once in a blue moon. I would rather have the compiler vendors spending time working on a better compiler than the standards group sitting around trying to justify their existence. IMHO, C/C++ has really come to the end of their extensible lifetime. It really needs to be rebuilt from the ground up and not have new features just hacked onto it. Tim Smith I'm going to patent thought. I have yet to see any prior art.
-
Tim Smith wrote: IMHO, C/C++ has really come to the end of their extensible lifetime. It really needs to be rebuilt from the ground up and not have new features just hacked onto it. Hear, hear. Brandon
-
Chris Losinger wrote: both are forcing you to work around limitations of the language. Well, yeah, and C# lets you do properties with get and set methods automatically called at appropriate times. But how much of this is a big advantage? Can you provide an example where code clarity is increased significantly by being able to return two values?
---
Shog9 Life seems pretty easy when it's from my easy chair And you're burnin up inside and no one cares...
Shog9 wrote: C# lets you do properties with get and set methods automatically called at appropriate times. But how much of this is a big advantage? I think "properties" let us write code in a more "human readable" fashion. Compare the two sets of statements below:
myForm.BackColor = red; Color clr = myForm.BackColor;andmyForm.setBackColor(red); Color clr = myForm.getBackColor();But I agree, these choices are merely based on convenience, that's all. -
std::vector :omg::rolleyes::laugh: Tim Smith I'm going to patent thought. I have yet to see any prior art.
laugh it up... what if you want to return 7 values, not all the same type? A: a "struct" is a workaround.
There's one easy way to prove the effectiveness of 'letting the market decide' when it comes to environmental protection. It's spelt 'S-U-V'. --Holgate, from Plastic
-
This is not a question about how to do something, per say, but is a question of opinion. Still, if anyone feels this post is ill placed, let me know, and I'll move it. :) I noticed a language on SourceForget the other day called Nice, that had an interesting feature called Tuples. Essentially, it allowed you to do this:
(int, int) FooBar()
{
return 5, 10;
}My question is what do you think about this in a language. Most of our languages have thus far only supported a single return value, where as Nice allows an arbitrary number of values to be returned. Thoughts? Jamie Nordmeyer Portland, Oregon, USA
This looks nice but how do i call this function ?
(int, int) a=FooBar(); //?? int b=a??+a??; :confused:i'm only pointer to myself -
Colin Davies wrote: The best way to find out how useful something is, isn't to add it, but to remove it. True, that. :) One of the things i miss most in VB are C's +=, *=, &= etc. operators... Never something i would have wanted prior to using C, but sure conspicuous when absent now...!
---
Shog9 Life seems pretty easy when it's from my easy chair And you're burnin up inside and no one cares...
Shog9 wrote: One of the things i miss most in VB are C's +=, *=, &= etc. operators... Sadly I miss those as well.
Nick Parker
Not everything that can be counted counts, and not everything that counts can be counted. - Albert Einstein
-
laugh it up... what if you want to return 7 values, not all the same type? A: a "struct" is a workaround.
There's one easy way to prove the effectiveness of 'letting the market decide' when it comes to environmental protection. It's spelt 'S-U-V'. --Holgate, from Plastic
-
That is what the VARIANT was for. :) Tim Smith I'm going to patent thought. I have yet to see any prior art.
ah.. the VARIANT. the deepest chasm in the Valley of Dangerous Practices. i fear the VARIANT and all its evil offspring. nothing but pain and suffering down that road.
There's one easy way to prove the effectiveness of 'letting the market decide' when it comes to environmental protection. It's spelt 'S-U-V'. --Holgate, from Plastic
-
This is not a question about how to do something, per say, but is a question of opinion. Still, if anyone feels this post is ill placed, let me know, and I'll move it. :) I noticed a language on SourceForget the other day called Nice, that had an interesting feature called Tuples. Essentially, it allowed you to do this:
(int, int) FooBar()
{
return 5, 10;
}My question is what do you think about this in a language. Most of our languages have thus far only supported a single return value, where as Nice allows an arbitrary number of values to be returned. Thoughts? Jamie Nordmeyer Portland, Oregon, USA
-
Shog9 wrote: Eh, what's wrong with... both are forcing you to work around limitations of the language. what you really want to do is "return 2 values". it's similar to the way you can do "OO" in plain C by clever use of function pointers and structures to simulate objects. but, it's nothing like C++, where OO is built-in. -c
There's one easy way to prove the effectiveness of 'letting the market decide' when it comes to environmental protection. It's spelt 'S-U-V'. --Holgate, from Plastic
Well put, Chris. Zat's what I was thinking. Jamie Nordmeyer Portland, Oregon, USA
-
Shog9 wrote: One of the things i miss most in VB are C's +=, *=, &= etc. operators... Sadly I miss those as well.
Nick Parker
Not everything that can be counted counts, and not everything that counts can be counted. - Albert Einstein
Well, most of the users on here use C#, but VB.NET has included these operators. Unfortunately, ++ and -- aren't used (why, I don't know), and you can't overload them. Doh!!! Jamie Nordmeyer Portland, Oregon, USA
-
Well, most of the users on here use C#, but VB.NET has included these operators. Unfortunately, ++ and -- aren't used (why, I don't know), and you can't overload them. Doh!!! Jamie Nordmeyer Portland, Oregon, USA
Jamie Nordmeyer wrote: Well, most of the users on here use C#, but VB.NET has included these operators. Unfortunately, ++ and -- aren't used (why, I don't know), and you can't overload them. Doh!!! I know, as am I. I have only used VB.NET a few times, only enough to answer a few questions in their forum.
Nick Parker
Not everything that can be counted counts, and not everything that counts can be counted. - Albert Einstein
-
Chris Losinger wrote: pair will get you 2. how do you do 3, 10 or 50? I thought he only wanted 2. Someone else mentioned boost tupples. In my vast experience a pair is the most common requirement here by far.:) Neville Franks, Author of ED for Windows. www.getsoft.com Make money with our new Affilate program
But using a Tuple object, we're still returning only 1 value... an object. The idea of the tuple as presented in Nice is that you're physically returning 2, 3, or n number of values. You're not wrapping them in an object to fake it, you're physically passing back an int, and then a float, or whatever. Jamie Nordmeyer Portland, Oregon, USA
-
ah.. the VARIANT. the deepest chasm in the Valley of Dangerous Practices. i fear the VARIANT and all its evil offspring. nothing but pain and suffering down that road.
There's one easy way to prove the effectiveness of 'letting the market decide' when it comes to environmental protection. It's spelt 'S-U-V'. --Holgate, from Plastic
I haven't thought about Variants since I started using .NET. Now, to have them return to my memory... AAAAARRRRGGGHHH!!!! :omg::omg::omg::wtf::wtf::wtf: :-D Jamie Nordmeyer Portland, Oregon, USA
-
This looks nice but how do i call this function ?
(int, int) a=FooBar(); //?? int b=a??+a??; :confused:i'm only pointer to myselfI think it'd be something like:
int a, b;
(a, b) = FooBar();
Or maybe a special symbol other than parenthesis, perhaps brackets. Jamie Nordmeyer Portland, Oregon, USA
-
pair will get you 2. how do you do 3, 10 or 50? -c
There's one easy way to prove the effectiveness of 'letting the market decide' when it comes to environmental protection. It's spelt 'S-U-V'. --Holgate, from Plastic
-
Eh, what's wrong with:
struct blah_t { int i; int j; };
blah_t FooBar()
{
blah_t ret = {5,10};
return ret;
}or for that matter,
void FooBar(int& i, int &j)
{
i = 5; j = 10;
}Granted, Nice sounds concise, but it seems unnecessary given how often such a thing is necessary.
---
Shog9 Life seems pretty easy when it's from my easy chair And you're burnin up inside and no one cares...
Option one makes you perform a copy of the data, which is always expensive. The compiler may be capable of optimizing the copy away though -any thoughts? Christian Skovdal Andersen Don't mention the war...
-
Eh, what's wrong with:
struct blah_t { int i; int j; };
blah_t FooBar()
{
blah_t ret = {5,10};
return ret;
}or for that matter,
void FooBar(int& i, int &j)
{
i = 5; j = 10;
}Granted, Nice sounds concise, but it seems unnecessary given how often such a thing is necessary.
---
Shog9 Life seems pretty easy when it's from my easy chair And you're burnin up inside and no one cares...
Shog9 wrote: Granted, Nice sounds concise, but it seems unnecessary given how often such a thing is necessary. It happens enough to be annoying. I usually use std::pair or one of my handcrafter stdex::triplet, std::quadruplet, etc. Maybe I should start using boost for this too. :) -- This space for rent.
-
Jamie Nordmeyer wrote: My question is what do you think about this in a language. I think it's a darn useful feature. Some might think "How often would I use it?" But if it was added to C++ I'm sure I'd find more and more uses for it. The best way to find out how useful something is, isn't to add it, but to remove it. :-) Maybe, I should use the Boost version. :-) Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
Colin Davies wrote: The best way to find out how useful something is, isn't to add it, but to remove it. So true! You are the wise man of CodeProject Colin, you have realized that by now, haven't you? <less-serious>If we could find two more wise men and a pregnant virgin, we could setup a CodeProject christmas theatre show.</less-serious> :) -- This space for rent.
-
But using a Tuple object, we're still returning only 1 value... an object. The idea of the tuple as presented in Nice is that you're physically returning 2, 3, or n number of values. You're not wrapping them in an object to fake it, you're physically passing back an int, and then a float, or whatever. Jamie Nordmeyer Portland, Oregon, USA
Whats the difference? The only difference is syntax... -- This space for rent.