struct Foo { int Bar; }; no more has a constructor/destructor than "int" does. And it doesn't have an assignment operator at all, while "int" has a pile of them
Sure Foo has an assignment operator. It's perfectly fine to write:
Foo a = { 1 };// this isn't a ctor, it's aggregate initialisation Foo b; b = a;// assignment - b.Bar now = 1
That's the way it works in C, too (which is at least part of the reason that C++ gives you the default memberwise assigment operator "for free")
It even has a copy constructor...
Foo a = { 2 }; Foo b( a );// copy construct - b.Bar now = 2
The fact that you didn't write these operations don't mean they don't exist.
Technically, Foo also has a default implicitly declared default constructor - see ISO/IEC 14882:2003 section 12.1 for details. It just doesn't do much (which is why it's called a trivial constructor). The same applies to the destrictor (section 12.4 of the same document)
Two things: 1) If someone COULD throw a dictionary at 100mph, I suspect it might be considered evidence of having a HELL of a pitching arm. Move over Randy Johnson (and the rest of the "100mph club")
2) I have a pocket dictionary that seems to mass a little less that a baseball (based purely on how it feels in my hand - I haven't weighed it). Sure, it's not as aerodynamic - but if you'd read my original post you'd realise I was ignoric friction effects.
Let's make some assumptions: 1) No friction (it makes the calculations messy, and the assumption errs in your favour) 2) You can hurl a dictionary at 100mph (unlikely, I suspect - unless you're a major league pitcher) 3) The 0.05 seconds is pure transmission time and ignores your wind up (again, this is in your favour)
That makes your room about 7ft 4in across. I suggest you take the pitching job and move to a bigger apartment...
Bandwidth hasn't been the only bottleneck for quite some time. Having high throughput between two points on a connection doesn't mean you have hige throughput across the entire connection. If somebody's server is at the end of two tin cans and a bit of wet string, it doesn't matter how fast your local connection is...
I think an 80% mandation (is that even a word?) Not in English; you mean an "80% mandate".
You leave 20% left over for missions-critical applications [...] But the remaining 80%, which represents mostly desktop applications for clerks and whatnot, will be running on OSS
I read this to imply that you don't believe OSS to be suitable for mission-critical applications? Is that really what you mean?
Actually, the real problem with the alien weapons was that they were, in fact, open source - and all the humans were too busy bucking for management to dabble with anything that's clearly that worthless - after all, if it's free (as-in-beer), how can it be any good?
Just to give his comment some context, there's been a series of TV ads recently in the UK (where the survey was done), for which the tagline was "it does exactly what it says on the tin". I presume that's what Mr Crabtree's comment refers to.
> So it means that they may as well send a terrorist's luggage on another flight. Sure - but I doubt the terrorists involved in last September's attacks were all that worried about where their luggage was going to end up...
Slashdot Mirror
struct Foo { int Bar; };
// this isn't a ctor, it's aggregate initialisation // assignment - b.Bar now = 1
...
// copy construct - b.Bar now = 2
no more has a constructor/destructor than "int" does. And it doesn't have an assignment operator at all, while "int" has a pile of them
Sure Foo has an assignment operator. It's perfectly fine to write:
Foo a = { 1 };
Foo b;
b = a;
That's the way it works in C, too (which is at least part of the reason that C++ gives you the default memberwise assigment operator "for free")
It even has a copy constructor
Foo a = { 2 };
Foo b( a );
The fact that you didn't write these operations don't mean they don't exist.
Technically, Foo also has a default implicitly declared default constructor - see ISO/IEC 14882:2003 section 12.1 for details. It just doesn't do much (which is why it's called a trivial constructor). The same applies to the destrictor (section 12.4 of the same document)
K 2, Brute?
/. readers ...)
(Or was that a bit classical for
Two things:
1) If someone COULD throw a dictionary at 100mph, I suspect it might be considered evidence of having a HELL of a pitching arm. Move over Randy Johnson (and the rest of the "100mph club")
2) I have a pocket dictionary that seems to mass a little less that a baseball (based purely on how it feels in my hand - I haven't weighed it). Sure, it's not as aerodynamic - but if you'd read my original post you'd realise I was ignoric friction effects.
I'm glad I live in a country where my broadband connection is less than US$50 a month :)
Let's make some assumptions:
1) No friction (it makes the calculations messy, and the assumption errs in your favour)
2) You can hurl a dictionary at 100mph (unlikely, I suspect - unless you're a major league pitcher)
3) The 0.05 seconds is pure transmission time and ignores your wind up (again, this is in your favour)
That makes your room about 7ft 4in across. I suggest you take the pitching job and move to a bigger apartment...
Bandwidth hasn't been the only bottleneck for quite some time. Having high throughput between two points on a connection doesn't mean you have hige throughput across the entire connection. If somebody's server is at the end of two tin cans and a bit of wet string, it doesn't matter how fast your local connection is...
How long will it take to burn a truckload of DVDs anyway?
Not that long. You just need a can of gas (although the truck might have some in the tank), and a Zippo...
It seems that way because it is that way
I code faster at home than at work primarily because the coffee is better...
That's because sweeping generalisations are always wrong...
The problem wasn't shoes, it was shoe shops. MUCH scarier...
Linux can't do everything.
It can if you apply the latest patch to "everything"...
Where do you buy software for a disposable razor?
You never had cause to worry - American politicians are easily as stupid as everyone elses (which is quite an achievement, when you think about it ;))
I think an 80% mandation (is that even a word?)
Not in English; you mean an "80% mandate".
You leave 20% left over for missions-critical applications
[...]
But the remaining 80%, which represents mostly desktop applications for clerks and whatnot, will be running on OSS
I read this to imply that you don't believe OSS to be suitable for mission-critical applications? Is that really what you mean?
> I miss the BBS days where you needed about 10 compression programs.
;) Those where the days...
And then you glued them alltogether with Shez?
(I just used to REARJ everything into ARJ format myself)
But since 99.9% of /. readers never follow the links and assume that the whole story is in the headline, who cares?
Actually, the real problem with the alien weapons was that they were, in fact, open source - and all the humans were too busy bucking for management to dabble with anything that's clearly that worthless - after all, if it's free (as-in-beer), how can it be any good?
> I do believe that older, less capable formats generally always make way for the newer, better formats [...].. Win95 to WinNT to WinXP
Dude, you forgot Win(whatever) to Linux!
Except for the twice life sized one the space aliens have...
Just to give his comment some context, there's been a series of TV ads recently in the UK (where the survey was done), for which the tagline was "it does exactly what it says on the tin". I presume that's what Mr Crabtree's comment refers to.
> I'd just like to know how he attached the spring to the e-mail.
...
Content-Type: misc/Spring
Content-Transfer-Encoding: base64
Content-Disposition: attachment
> I thought it was Tuesdays.
/. will get an obscure)
Nope. Tuesday's gone (with the wind).
o
O
(Thinks: No-one on
(Lynyrd Skynrd reference like that. Sigh )
I just hope it's succesful
> So it means that they may as well send a terrorist's luggage on another flight.
Sure - but I doubt the terrorists involved in last September's attacks were all that worried about where their luggage was going to end up...