Skip to content

Settings and activity

2 results found

  1. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Mice  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kent Fredric commented  · 

    Nope, tested prototypes, don't do the trick. You also have to get around odd use cases like

    first { } method() # which is apparently broken by the &@ prototype.

    Like I said, you really *do* have to reach for dark magic to solve this issue normally, and lazyness and "Cant I just do it in perl" and "I can't touch the original code to fix this" and "original code doesn't want XS nasties" ==> Well, the best I can do is create a new package, so I can either re-implement all of List::* myself somehow, or wrap it all myself somehow (ie: create a clone of ::AllUtils with XS nasties )

    Or, it could just be a critic policy. Which works.

    An error occurred while saving the comment
    Kent Fredric commented  · 

    I threw this idea your way just in case I don't find the tuits myself to do it =).

    Kent Fredric shared this idea  · 
  2. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Mice  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Kent Fredric commented  · 

    This would supersede the proposed patch to cpanm, and also get around the notion that cpanm many never support reporting tests natively, because upstream have said they wont.

    With this approach, they don't need to, as long as the tool can mangle/handle cpanm, it will work.

    Kent Fredric shared this idea  ·