Modules, Versioning, and Beyond

2001-07-29 Thread Bryan C . Warnock
e use (or perhaps, one that we haven't used yet) from within our scripts, preferrably without having to add explicit code to do so. GUIDs Gurusamy, in his discussion about what he feels Perl 6 should be, proposed GUIDs (Global Unique IDs). Although he didn't go into detail, GUIDs would be one way to encode both version and authoring details much like what Larry wanted. But here we have the chicken-and-the-egg problem. GUIDs are excellent for C2C communications, but horrible for H2C communications. And you'd still need to derive some sort of structure for the modules to coexist on disk. -- Bryan C. Warnock [EMAIL PROTECTED] -- Bryan C. Warnock [EMAIL PROTECTED]

Re: Modules, Versioning, and Beyond

2001-07-30 Thread Bryan C . Warnock
they export) being introduced into the calling code lexically. If that is the case, then you needn't worry about the exporting or the code collision. Unless you do something bad. The only real difference is that you can unexport, and essential pop the lexicals before end-of-scope. -- Bryan C. Warnock [EMAIL PROTECTED]

Re: Perl 6 modules plan

2001-08-09 Thread Bryan C . Warnock
ble. [1] http:[EMAIL PROTECTED]/msg03359.html , about two-thirds down. [2] http:[EMAIL PROTECTED]/msg03366.html -- Bryan C. Warnock [EMAIL PROTECTED]