Here I am, at the end of my E-journey.
What have I learned?
The existance of great ideas. I don’t really like E’s syntax but the ideas behind and beyond this language are great. The capability security model is stupid-proof and 100% secure. It’s a pity nobody uses it. As far as I know Palladium is a capability [...]
Filed in Uncategorized
|
Tagged e
|
Capabilities
E uses capability based security to supply both strong security and broad flexibility without incurring performance penalties. Capabilities might be thought of as the programming equivalent of physical keys
E makes use of the Principle of Least Authority (POLA) to ensure that it gives no more authority that the other part needs.
In the real physical world, [...]
Filed in Uncategorized
|
Tagged e, security
|
I released a you-should-have-released-it-months-ago version
What’s new?
SQLite 3 support
What’s changed?
Requires Rails 1.0
Atom 0.3 feed dropped
http://rebbin.berlios.de/
A live version here: http://pasteserver.net/
Wednesday, March 15, 2006
Just received them from Amazon.
Only listened to Kind Of Blue yet, three times. Gorgeous.
Filed in Uncategorized
|
Tagged misc
|
E programs never block. They never just sit and wait around for results.
It this just a dream ?
Filed in Uncategorized
|
Tagged e
|
A promise is the result of an eventual send to an object:
[code lang="javascript"]
def carVow := makeCar <- ("Mercedes")
carVow <- moveTo(2,3)
[/code]
“<-” is the eventual send operator.
Now you can start making eventual sends to the promise as if it were the object itself.
The “when-catch” clause is used to wait for the resolution of a promise:
[code lang="javascript"]
def temperatureVow [...]
Filed in Uncategorized
|
Tagged e
|