channel-specific definitions with one-way transitive trust/inherit feature

[diakopter]

17:48 < dpk> diakopter, pong
17:48 < Tene> C's better anyway, because 99 is much higher than 6
17:49 < Tene> although Perl 6 is catching up quite a bit in recent years, with C11
17:49 < diakopter> dpk: hi :) feature request, or ignorant question if it's already got the feature
17:49 < dpk> fire away
17:49 < arnsholt> nwc10: Oh. Right. For some reason I thought Perl used flex
17:49 < arnsholt> In that case, I agree =)
17:49 < arnsholt> I was just a bit curious about flex, since it's kinda sorta C, but mostly not
17:49 -!- PacoAir [~PacoAir@139.Red-80-36-122.staticIP.rima-tde.net] has joined #perl6
17:51 < arnsholt> I have a fond memory of doing a simple data munging flex. My friend did it using Common Lisp and spent way much more
                  time, writing lots more code and ending up with a program that was dog slow =D
17:51 < arnsholt> I had 10 lines of flex \o/
17:52 < diakopter> channel-specific definitions -    .? Foo is blah blah blah      .? Foo    <-- to retrieve definition    and a way to
                   append multiple [or expanded] definitions instead of replace existing - also with particular syntax for replace [as
                   opposed to default append] you don't need a "confirm" on replace.  Also, a way to enable one-way inherit of
                   definitions, with transitivity. So this channel could share/modify the same set of definitions if *both* ...
17:52 < diakopter> ... trusted/inherited each others'
17:54 < diakopter> dpk: ^
17:54 < diakopter> enabling the trust is admin-only command obviously...
17:55 < dpk> hmm. i'll make a note. i can see why that might be useful (channel rules and stuff)
17:55 < diakopter> er, "... the same set of definitions *[as another channel] ..."
17:56 < diakopter> it's used a lot on help channels for shortcuts to FAQ answers
17:56  * dpk nods
17:56 < diakopter> or acronym explanations
17:56 < dpk> .acronym AAAAA
17:57 < yoleaux> AAAAA could stand for: American Association Against Acronym Abuse; Association Amicale des Amateurs d'Andouillettes
                 Authentiques; AHo's Amazing Atlas of Antibody Anatomy; American Association Against Alliteration Abuse
17:57 < diakopter> .acronym A
17:57 -!- shinobicl [~shinobi_c@ip-238-226-107-190.nextelmovil.cl] has joined #perl6
17:57 < diakopter> .acronym AA
17:57 < yoleaux> A could stand for: About; To; Adult; Are; Amateur; Year; Area; Ass; Account; Action; Advanced; Individual; Advanced
                 Digital Audio; First in Series; Away; Author; Association; Ask; Blood Type; Active; Excellent; American Bank Note
                 Company; Anna; Answer; Article; Accept
17:57 < yoleaux> AA could stand for: Automobile Association; Ana; Battery Size; Associate in Arts; As Above; Architectural Association;
                 Athletic Association; Asian American; Bra Size; Administrative Assistant; Anti-Aircraft; Aruba; Amino Acid; Atomic
                 Absorption
17:57 < diakopter> *sigh
17:58 < diakopter> well, these would be channel-specific acronyms. :)
17:59 < dpk> ok, i'll think about it. if you want that functionality right now though, Bucket (https://github.com/zigdon/xkcd-Bucket)
             provides some of that functionality … i don't think it does channel-specific keyword associations, though …
18:00 < diakopter> wow, a 2100-line subroutine
18:00 < diakopter> nice.
18:01 < diakopter> jnthn: ^ example of extreme programming
18:01 < xilo> diakopter: all my whys
18:01 < diakopter> (bucket.pl)
18:02 < diakopter> personally, I don't see anything wrong with it... it doesn't indent horribly much; it's just a very long inlined
                   command-pattern
18:03 < diakopter> but I know others would disagree
18:03 -!- BigBear [~chatzilla@mail.uk.om.org] has joined #perl6
18:03 < japhb> timotimo: Sorry for bad error report re: nqp::copy (I was bleary tired after finding the two problems in the first place,
               since one was hiding the other).  Did you get it figured out yet?
18:03 < yoleaux> 08:20Z <jnthn> japhb: it's not so simple as nqp::usecapture 'cus it hllize's arguments and handles natives too. I
                 suspect it may stay as an op and we just implement it in the set of extra ops we'll add for JVM, so it'll get an
                 nqp::p6arglist op or so (should not say RPA in nqp:: op names).
18:03 < yoleaux> 08:20Z <jnthn> japhb: CCLASS_PRINTING being missing is just an oversight; should be converted too
18:03 < yoleaux> 08:21Z <jnthn> japhb: other things may use Q:PIR and pir:: outside of Rakudo, so that can live a bit longer, but we may
                 want to make it require a pragma and spend a while warning if the pragma ain't there.
18:04 < japhb> jnthn, understood on all three.  #2 (CCLASS_PRINTING) is a good LHF for someone with tuits in the next few hours ....
18:04 < dpk> diakopter: i have to go now, but, so i remember, could you file a feature request at https://github.com/dpk/yoleaux/issues
             ? thanks
18:04 < diakopter> sure

[diakopter]

01:10 < yoleaux> 00:53Z diakopter: ok, after some consideration, i've decided that, while the feature may well be
useful, it doesn't fit well with yoleaux's general purpose and this particular task is best left to
another bot, imo. thanks for the suggestion though!