Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Comment: Re:this already exists (Score 1) 256

by TheCarp (#49630259) Attached to: USBKill Transforms a Thumb Drive Into an "Anti-Forensic" Device

Generally data is supplied in the form of disk images, and large binders full of reports. I have seen the stacks in a friend's office who did some forensics defense work. He basically got paid big bucks to load up images of people's files and explain technology to lawyers.

In fact, if you look back just a few weeks here on /. there was a story about exactly what you are saying....but.... the lawyer caught on and caught the police in the act.... he even said he had NEVER received evidence as physical equipment before, always images, which is why he was suspicious.

Comment: Re:nonsense (Score 1) 224

by Cajun Hell (#49629353) Attached to: The Medical Bill Mystery

Yes, there are too many market forces keeping the prices down. It's a race to the bottom. People, stop all this miserly shopping for the cheapest medical care! Sure, your tiny Wal-Care bills look attractive but have you considered that if you keep doing this, you're going to cut more mom'n'pop providers out unless they are also able to viciously cut costs?

We need to put Wal-Care (and other super-slim-margin health care providers) out of business, in order to protect the health care profession!

Comment: Re:Technically C++ (Score 1) 223

My Slashdot username predates my current employment arrangement by about 5 years, I think. But, yeah. Back then I ran FreeBSD (which is where the name is from) on my servers, and Gentoo on my desktop. Things change :) (well, some of them; some of my home servers are still FreeBSD - ain't broken and all that...)

By now, though, it's not really all that surprising, given the amount of work specifically targeting other platforms (Linux among them) happening throughout the company. My team, for example, is actually specifically looking for people with a Linux background right now, because we're building a service running on it, using Docker containers for isolation.

Comment: Re:Technically C++ (Score 1) 223

In this particular case I just happen to know exactly what they were thinking when they were implementing this feature, because they are my colleagues (even if I don't work on the team that works on C++) :) The list of features that they did was based on some specific libraries that they had most complaints about on Windows, and then filtered down further based on ease of implementation. If I remember correctly, one major beneficiary of those changes is supposed to be ffmpeg.

This all might make more sense if you remember that Office in some incarnation or the other now ships across three non-Windows platforms (OS X, iOS and Android), then there is the OneDrive client etc. Basically there's a whole bunch of stuff that has suddenly gone cross-plat in the past couple of years, and that's a lot of C++ code that now has to play ball with the libraries that are the de facto standard outside of the MS ecosystem. In many cases, once you start doing that, it makes sense to use the same library on Windows as well, but then you start running into those conformance issues with C99.

The other aspect is that we want people to write cross-platform C and C++ code, because it's the kind that, right now, is most easily portable between all mobile platforms - and seeing where Windows phones and tables are in terms of popularity relative to iOS and Android, MS has to encourage portability as a way to get more apps ported to Windows. You see things like Apache Cordova tools and Clang/LLDB support in VS 2015 for the same reason - they make it easier to write Android apps, for example, but more importantly, the way they encourage writing those apps just happens to be the one that emphasizes portable code. Now that is more geared towards C++, but the question of popular libraries written in C also comes up there.

Comment: Re:Technically C++ (Score 1) 223

VS2013 seems to understand a bit more or C99, but that isn't because Microsoft would suddenly have started caring about their C compiler. Their C++ compiler got a bit of an upgrade wrt. more recent changes to the C++ standard, and the C compiler understanding a few C99 idioms is largely a side-effect/waste-product of that process.

Not quite. VS 2013 actually saw a bunch of C-specific C99 features such as designated initializers for structs. The main reason why this was done is because there are now quite a few popular open source libraries that use those features, and VC is the only compiler that cannot handle them, which made it a pain to port them to Windows.

Comment: Re:That's C code (Score 1) 223

stdio.h and cstdio are both valid in C++. However, there is a slight difference - cstdio is only guaranteed to define the identifiers that it provides in namespace std, while stdio.h makes the same guarantee only for the global namespace. In practice, they are usually both backed by the same header that does both, so you'll get both - but relying on that is non-portable. Since he doesn't use std:: to refer to those identifiers, "stdio.h" is the correct header for him to include.

Comment: Re:That's C code (Score 1) 223

"stdio.h" searches the directory containing the current source file first, then the include directories.

The standard itself doesn't have any notion of "directory containing the current source file" or "include directories", actually. It just says that "..." does some form of implementation-defined search, which, if it fails, falls back to <...>.

Comment: Re: That's C code (Score 1) 223

It's still not the same thing. In C, you can declare a function without specifying the argument types, but then define it with specific types in a different translation unit. In C++, the definition and the declaration must match - if you declare it as int foo(...), then you must also define it in the same way (which renders it effectively useless, since without any named arguments you won't have anything to pass to va_*).

Comment: LOL Microsoft (Score 1, Troll) 135

by Dunbal (#49624083) Attached to: Microsoft: No More 'Patch Tuesday' For Windows 10 Home Users
Windows 10. I have a, well, call him a friend, who works at Microsoft and has been forced to deal with the Windows 10 "beta" on his work machine for quite a while now. Apparently it's hard to keep productivity up when the damned thing keeps blue screening all the time. His opinion to me was that Windows 10 was the biggest piece of suckage Microsoft has produced to date. I bought some popcorn and am looking forward to release.

Comment: Re:this already exists (Score 1) 256

by Dunbal (#49624061) Attached to: USBKill Transforms a Thumb Drive Into an "Anti-Forensic" Device


Me neither so I won't play that game. Maybe the phrasing is different and all sorts of little details and lawyer tricks happen, but the jist is the same. It's one thing to have say IP logs of naughty things crossing the internet to your IP, and actually seeing the file on your hard drive and your fingerprints on the keyboard.

1 Mole = 007 Secret Agents