class F { public static void Main () { Button button = new Button (); button.Text = "Hello, World!"; button.Dock = DockStyle.Fill; button.DialogResult = DialogResult.OK;
Form form = new Form (); form.Controls.Add (button); form.ShowDialog (); } }
wait, who has Windows servers that use anything more than VGA drivers to display the login screen 24x7? the only time I hook up a monitor to our servers is to install the OS.
No, it's an array of pointers to an array of elements
This is the default definition of operator [], but you could easily overload it to do something else.
for example, you could easily write a set of templates such that array[row][col]=3 would result in array.set(row,col,3) and still maintain type-safety and efficiency.
you're forgetting your history. it was microsoft that introduced the concept of a configurable default browser and the 'use me as your default (yes/no/don't ask)' dialog. and it was netscape that caused a fuss by overriding the default every time it started.
don't be so surprised. it sounds like a pretty efficient way to kill of open-source projects. under this kind of legislation, Microsoft would just create a 'product liability' division, reduce the complexity of its products, increase testing, and hike up the price of their products to cover liability insurance (more than a third of the cost of a football helmet is liability insurance, heck, McDonalds increased their prices to insure themselves against fuckwits sueing them for spilling coffee on themselves). open-source developers and smaller ISV won't be able to survive in such a market.
the video on channel9 a while back with the team developing this said they plan to support common browsers, they specifically mention firefox. i believe the betas are IE only, though.
this guy can build systems involving some of the most advanced technology available, and yet he didn't realize that by opening both ends of the box you can simply push the contents out the other side.
or maybe we are all part of some Matrix-like simulation in someone else's universe.
Iain M. Banks extendes this into a religion in The Algebraist the premise of which is that if enough of the 'simulated' subjects believe that they are in a simulation then the simulation would be worthless and the people running it would just turn it off - a kind of cosmic Judgement Day, but without the judgement.
here is a good example of some very mature software that still has bugs. and it's very small. the problem with knowing the number of bugs in a piece of software is the assumption that you've found them all.
sure, but that case is the same for both camps (although statically-typed languages could potentially subclass 'integer' to a more restrictive set). the argument that static typing is more difficult is purely subjective, but I'd argue strongly against it. what happens, for example, if one of my teammates changes some key structure in a library. how do i know that my code that uses it is going to work? with dynamic typing there's no complete code analysis, but with static typing I have a tool that'll tell me exactly where the changes need to occur: it's called a compiler. as i said before, if you're writing trivial programs then dynamic typing is great, hell bash is great, but if you're working on a large project in a large team over many years then it just doesn't cut it.
Slashdot Mirror
...and apparently they even managed to spell it wrong.
// 10 lines in c#
using System.Windows.Forms;
class F
{
public static void Main ()
{
Button button = new Button ();
button.Text = "Hello, World!";
button.Dock = DockStyle.Fill;
button.DialogResult = DialogResult.OK;
Form form = new Form ();
form.Controls.Add (button);
form.ShowDialog ();
}
}
microsoft isn't deprecating OpenGL for fullscreen apps, they're just not supporting windowed OpenGL on a 3D-composited desktop.
wait, who has Windows servers that use anything more than VGA drivers to display the login screen 24x7? the only time I hook up a monitor to our servers is to install the OS.
new?
for example, you could easily write a set of templates such that array[row][col]=3 would result in array.set(row,col,3) and still maintain type-safety and efficiency.
yup, they'll have to take firefox out of debian since it's covered by patents.
I always thought he fell of because Dick Cheney wasn't there to hold the handlebar for him.
you're forgetting your history. it was microsoft that introduced the concept of a configurable default browser and the 'use me as your default (yes/no/don't ask)' dialog. and it was netscape that caused a fuss by overriding the default every time it started.
did a quick search, Weyerhauser grows 230 million new trees anually
the big joke is that the government is cutting budgets left right & center while pouring money into their back packets in iraq.
I wonder if they'll take the day off when they're done.
well worth a look if you can't make it there yourself.
does an INI file system handle multiple apps concurrently writing to the same file?
are your INI files indexed by key name for performance?
do they easily store hierarchical data efficiently?
do they have support for per-key permissions?
are they easily backed-up and versioned by the operating system?
the windows registry does all of these.
It was all part of Microsoft's new subtle plan to subvert Java in the marketplace... one lecture at a time...
don't be so surprised. it sounds like a pretty efficient way to kill of open-source projects. under this kind of legislation, Microsoft would just create a 'product liability' division, reduce the complexity of its products, increase testing, and hike up the price of their products to cover liability insurance (more than a third of the cost of a football helmet is liability insurance, heck, McDonalds increased their prices to insure themselves against fuckwits sueing them for spilling coffee on themselves). open-source developers and smaller ISV won't be able to survive in such a market.
the video on channel9 a while back with the team developing this said they plan to support common browsers, they specifically mention firefox. i believe the betas are IE only, though.
wouldn't work. nobody in their right mind would chose anything but a "0". i'd buy a copy of the first non-"0" package, find a bug and sue.
The second rule of MySQL club is a foreign key constraint with cascading deletes. oops.
The mind boggles.
Iain M. Banks extendes this into a religion in The Algebraist the premise of which is that if enough of the 'simulated' subjects believe that they are in a simulation then the simulation would be worthless and the people running it would just turn it off - a kind of cosmic Judgement Day, but without the judgement.
I wonder if it's possible for a toroidal star to form around a bloack hole?
here is a good example of some very mature software that still has bugs. and it's very small. the problem with knowing the number of bugs in a piece of software is the assumption that you've found them all.
sure, but that case is the same for both camps (although statically-typed languages could potentially subclass 'integer' to a more restrictive set). the argument that static typing is more difficult is purely subjective, but I'd argue strongly against it. what happens, for example, if one of my teammates changes some key structure in a library. how do i know that my code that uses it is going to work? with dynamic typing there's no complete code analysis, but with static typing I have a tool that'll tell me exactly where the changes need to occur: it's called a compiler. as i said before, if you're writing trivial programs then dynamic typing is great, hell bash is great, but if you're working on a large project in a large team over many years then it just doesn't cut it.