在 2006/7/11 下午 11:52 時,Bob Rogers via RT 寫到:
But by "compile time" you both unambiguously mean "PIR compile time",
not "HLL compile time," since there's no HLL involved.  But an HLL
compiler always has the option of building a PIR constant at HLL compile
time [2], so that just leaves the case of human-generated PIR.  So it
seems that the real question is this:  Does PIR have a need to be an
eval-during-compilation language in its own right?

Yes. :immediate is only useful for hand-written PIR, not compilers targeting PIR; contrary to the appearance, it is useless for implementing BEGIN{}- like semantics for HLLs,
let alone unifying their semantics in some way.

So far we have been enable to produce a use case that requires unbounded evaluation that interacts with the environment during :immediate time. However, Chip and Allison already said they would like to reserve this feature for some future, unanticipated applications, and that it's okay for PIR tools to say "we simply break down under :immediate".

I really cannot argue with that argument (essentially "let's punt and see"); therefore this ticket is probably best reserved until Parrot actually has a security model, in which time I'll then argue that :immediate should be subjected to severe restrictions.

Thanks,
Audrey

Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to