Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment Re:Groovy (Score 1) 667

The nice thing is that LINQ is just syntactic sugar. So the two cases are equivalent:

List<int> numbers = { 5, 383, 291, 274, 104, 184, 63 };
List<int> results = from n in numbers where n > 150 select n;
List<int> results2 = numbers.Where(n => n > 150);

If you like to write lambdas instead of SQL-like queries it works just as well and either is very expressive.

Comment Re:Because Snapdragon Is an ARM Processor! (Score 1) 125

Apple had the advantage of inheriting NeXT's already architecture-independent API, and all of their new code respected that. Unfortunately, Win32 is *mostly* source-compatible between architectures but not entirely - it's only recently that you start seeing explicit type sizes such as UINT32 instead of just UINT - you still often have to guess what that will be on your target architecture.

Apple also inherited the Mach-O format, which encapsulates code for different architectures into a single binary - core system libraries often have code for ppc, ppc64, i386, and x86_64 all in one. PE binaries don't have that luxury, so you often see multiple binaries per architecture - proggy_x86.exe and proggy_x64.exe, for example. Imagine the confusion that would cause for your average user with ARM thrown into the mix.

Comment Re:No - there are plenty of safer alternatives (Score 2, Insightful) 486

Or, better yet, if security really was the goal, develop a C-like language that was secure by design?

And then why don't you make it compile to non-native code, so you can do code analysis at runtime? Might as well give it a good standard library that uses all the features so people would try writing stuff. Of course, you can't name it C then, maybe you should give it a catchier name with some punctuation or other pun on the language.

Hey, wait a minute...

Slashdot Top Deals

God may be subtle, but he isn't plain mean. -- Albert Einstein

Working...