Forgot your password?
typodupeerror

Comment: That is not what the halting problem say (Score 2) 327

Sorry, but that is not what the halting problem say.

The halting problems state that "For any interesting property(In this example: "Is this robot code safe to run") there exists programs with this property, but where you can not prove that the program has the property.

That is: There exists robot programs which are safe to run, but where we can newer prove that they are safe.

And the general solution is to only run programs where we can prove that they are safe. This mean that we do reject safe programs because we can't prove that they are safe*, but it does not in any way change the programs which we can express. That is: For any program which is safe, but where safety cant' be proved, there exists a program which behave in exactly the same way for all input, but which is safe.**

*If we can't prove that a program is safe, then it is either because no such prof exists, or it is because we are not good enough to prove it.

**No this does not contradict the halting problem, due to the assumption that the program is safe. If the program is not safe, then the transformation will convert the program to a safe program which obviously will not do the same

Comment: Re:Oracle (Score 4, Informative) 146

by TheSunborn (#48102327) Attached to: Google Takes the Fight With Oracle To the Supreme Court

Nobody ever said that Microsoft could not ship their own version of the JRE, and Microsoft newer made their own JRE.

Microsoft distributed a modified version of suns jre, based on source code licensed from Sun. And it was sourcecode licerse, which gave Microsoft problems. If they had just made their own jre, anything would have been fine(Except for the fact that they might not have called it Java(tm)

Comment: Re:Stay out of our business then..... (Score 1) 993

Sorry, but that is just wrong. He wrote a better(Or worse, depending on who you ask. I would say better) init system, but the decision to use it and thus to wrack your* init system was taken by the different Linux distributions.

*And no it's not your init system. Using something does not make it yours. It would only be yours if you had your own distribution, and in that case you could continue to use what ever backward init system you wanted.

Comment: Re:Well, (Score 1) 113

by TheSunborn (#47263043) Attached to: Unisys Phasing Out Decades-Old Mainframe Processor For x86

When Eclipse is crashing with a segmentation fault, it is almost always in swt. So the problem is with the native code which swt calls in order to interface with the underlying operation system.

That can only be solved by writing the entire Operation system in a safe language, but nobody is working on that.

I have newer seen Eclipse segfault outsite swt code.

Comment: Re:Compatibility is no problem, before or after sw (Score 1) 636

by TheSunborn (#47153879) Attached to: Apple Announces New Programming Language Called Swift

Don't this code have the problem that you call some_work from the gui thread, and thus will block all updates of the graphics userinterface while some_work is running?

That problem can be solved, but it is always things such as long running tasks, and async callbacks which causes problems. Especially if you need to populate the gui with the work from some_work, while some_work is still doing its work.

"Out of register space (ugh)" -- vi

Working...