Re: Dijkstra's Methodology for Secure Systems Development

2014-09-19 Thread Ian Grant
On Fri, Sep 19, 2014 at 7:17 PM, Ian Grant wrote: a bunch of stuff, and added: I forgot to add "you fucking ignorant jumped-up little prick!" So now you have _textual evidence_ that I really am impolite :-) Best wishes Ian

Re: Dijkstra's Methodology for Secure Systems Development

2014-09-19 Thread Ian Grant
Hi Panicz, What country do you live in at the moment? I ask because it makes a difference sometimes to know someone's background. I live in Bolivia. I am stateless, i.e. an illegal alien, and because of that have no source of income. I live on money borrowed from friends and family. My material p

[PATCH 1/1] Add "&" asm constraint modifier to ASM_MUL outputs

2014-09-19 Thread Rob Browning
Without this change, building for arm{hf,el} with gcc-4.9 (Debian 4.9.1-14) fails as follows: /tmp/ccdZTkXQ.s:14591: rdhi, rdlo and rm must all be different Thanks to Mark H Weaver for the suggestion. --- This should apply against 2.0.11. libguile/vm-i-scheme.c | 2 +- 1 file changed, 1 i

Re: Dijkstra's Methodology for Secure Systems Development

2014-09-19 Thread Panicz Maciej Godek
Hi. I've observed that some time ago you started sending tons of revolutionary ideas regarding the way the software should be written, and crtiticising the current practices. I am not in the position to refer to those ideas, because I didn't manage to comprehend them fully (although I am trying to

Dijkstra's Methodology for Secure Systems Development

2014-09-19 Thread Ian Grant
I hope this will provoke some new ideas about how to develop secure systems software. Thesis: The Software Development Process Itself is THE Major Security Vulnerability in Current Computing and Communications Practices This is because feasibility of the process depends entirely on re-use of conc

Re: [patch] literal arrays in master

2014-09-19 Thread Daniel Llorens
Now with a test. The first patch makes most of test-suite/tests/arrays.test run under both the compiler and the interpreter. It produces a large amount of errors under the compiler. The next two patches are the same as in the last email and fix these errors. However, it's interesting to me tha