Hi again,
While reading the progress repot I also looked at the code of the
compiler to get a feeling for what it can and cannot do.
Please correct me if I'm wrong, but it seems to go through a number of
standard phases not related to cryptography. Then there are these
three phases:
* Checking o
Hi Janus and everybody else,
I have now read the progress report and had a look at the PLAS paper:
http://www.daimi.au.dk/~fagidiot/fagidiot/download/jdn-progress.pdf
http://www.daimi.au.dk/~fagidiot/fagidiot/download/smcl-plas07.pdf
and of course I have lots of questions... :-)
I am confus
"D. J. Bernstein" <[EMAIL PROTECTED]> writes:
> Let me emphasize that this is just the cryptographic part of NaCl,
> and just an initial prototype. We're much more feature-complete than
> was scheduled for this point but there's also quite a lot more to
> do. Right now the prototype is in internal
Brian Graversen <[EMAIL PROTECTED]> writes:
Hi Brian
>> Then I guess we could identify it by the ID of the GFElement object
>> holding it. GFElements are immutable. By ID I mean the output of
>> id(e) where e is a GFElement -- I don't know what that maps to on
>> the C side of things, but the id(