P: A programming language for asynchrony, fault-tolerance and uncertainty
1–10 of 42 posts
Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#2Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#3P got its start in Microsoft software development when it was used to ship the USB 3.0 drivers in Windows 8.1 and Windows Phone. These drivers handle one of the most important peripherals in the Windows ecosystem and run on hundreds of millions of devices today. P enabled the detection and debugging of hundreds of race conditions and Heisenbugs early on in the design of the drivers, and is now extensively used for driver development in Windows.
Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#4https://github.com/p-org/P/blob/master/Doc/Manual/pmanual.pd...
Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#5Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#6It's worth noting that this isn't just a research language -- it's used in practice for writing drivers: P got its start in Microsoft software development when it was used to ship the USB 3.0 drivers in Windows 8.1 and Windows Phone. These drivers handle one of the most important peripherals in the Windows ecosystem and run on hundreds of millions of devices today. P enabled the detection and debugging of hundreds of…
As someone who has been thinking a lot recently about SPARK/Ada and "free" formal verification, can anyone tell me how this language compares on that front? If I write a P program, do I get the ability to "prove" its correctness?
Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#7Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#8Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#9At last, the long awaited successor to C, at least in the naming convention that assumes P comes after C because of BCPL. (Apologies to Walter Bright: No inference should be drawn that D was not also a good name for that sequence.)
Re: P: A programming language for asynchrony, fault-tolerance and uncertainty
#10At last, the long awaited successor to C, at least in the naming convention that assumes P comes after C because of BCPL. (Apologies to Walter Bright: No inference should be drawn that D was not also a good name for that sequence.)