From: John B. <joh...@ne...> - 2000-07-27 11:55:58
|
> > Would a reasonable approach to be to have 'compile' and 'decompile' > > methods in Convert::ASN1 which convert between 'readable' :-) ASN.1 and > > something nearer the internal representation? Then, as you say, do a > > 'compile' on install or first run and save the results? > > That is exactly what I was refering to. Nod. Just making sure I understood. > > (I guess there > > isn't a sensible place to keep an on-disk cache of compiled ASN1 > > definitions). > > Huh? alongside the .pm file. Sorry - I meant a 'transparent' cache of recently used ASN.1 definitions. Given a writable scratch area the Convert::ASN1 could in principle check to see if a compiled version exists whenever a request to load a set of ASN.1 definitions comes in. That way the modules/apps which use it would not need to explicitly save a compiled version at install time. Almost certainly not worth the effort, though. However, such a 'standard scratch area' for modules might be an interesting idea to feed into future perl6 lib discussions (the CPAN module would benefit, for one). I don't think its a good time to bring it up on perl6-bootstrap though :-) regards, jb |