user-pic

byterock

  • About: Long time Perl guy, a few CPAN mods allot of work on DBD::Oracle and a few YAPC presentations
  • Posted Moose Still gets a A to byterock

    It is follow-up day here in the Moose-Pen

    Having gotten 100% in Database::Accessor it is time now to see what my coverage level with Driver::DBI. On the first run I got;


    ---------------------------- ------ ------ ------ ------ ------ ------

  • Posted A++ Moose to byterock

    Still in cover mode here in the Moose-Pen

    I found another sub that was not being tested seem I never call 'da_warn' in my tests.

    This one is a little special;


    sub da_warn {
    my $self = shift;

  • Posted The Mighty Meta Moose to byterock

    Find and fix a bug day here in the Moose-Pen

    The great thing is the new tests I added to fix up my subroutine covers as reported by Delve::Cover revealed that I may have two new bugs in Database::Accessor.

    The two fails were;



    no…

  • Posted Back in the Moose Track to byterock

    It figured it out day here in the Moose-Pen


    Well I really should bow my head in shame again as I got the whole Devel::Cover concept backwards. I thought that changing the code in my application would change the results of cover. Well I was dead wrong on that some further reading …

  • Posted Moose Can't get a break to byterock

    Its start the long releases cycle here at the Moose-Pen

    Today I am going to examine some of the results I got from my 'Devel::Cover' run.


    ffile stmt bran cond sub pod time total
    lib/Database/Accessor.pm 94.4 80.0 88.8 9…

  • Posted Moose Take a Bow to byterock

    Another test day here in the Moose-Pen

    Today I am going to go though all the tests in my Driver::DBI and see what explodes

    Not really expecting a good run I was plesenlty surprised when I got;


    \t\20_fields.t (Wstat: 512 Tests: 88 …

  • Posted Full Monty Moose to byterock

    Its big change check-in day here in the Moose-pen

    I think there will be very little new code today but I did incorporate a large volume of changes. First I dropped 'Database::Accessor::Roles::AllErrors' as I no longer see any DAD writer ever having any user for it not that it does not th…

  • Posted Every Moose has a bad day. to byterock

    Another sad day in the Moose-Pen

    Not a good way to start another year of blogging as I was reviewing my tests and when I got into '47_dynamic_gathers.t' I was getting a duplication on the number of conditions on a gather which is not a good thing.

    Somewhere in the last few days I…

  • Posted Yearling Moose to byterock

    Final final final clean up day here in the Moose-Pen

    Just a quick postette today cleaning up the last of my messages on my error retruns. Starting with this one;


    'Database::Accessor Database::Accessor::add_condition Error:
    The following A…

  • Posted Moose at the edge to byterock

    Its get back on track day here Moose pen.

    I left off with the add_sort and did some refracting that when a little awry but I did get back on track. As it stands I have this original


    sub _element_coerce {
    my ($hash) = @_;
    my $…

  • Posted Moose Lights up to byterock

    Is may be the end of the errors Day here in the Moose-Pen.


    I spen quite a bit of time mulling over the various options and possible solutions to the rater large mess I made yesterday with my recursive call to a eval.

    I did manage to do a very long coded version where de-fact…

  • Posted Moose in a Dark Place to byterock

    Still stuck in error land in the Moose-Pen.

    As I finally got the 'add_condition' to work I still needed to add in a few more tests for the other three 'dynamic' attributes, gather, link and sort.

    Well I started with the easiest first 'sort' and on the 'undef' I am getting the now …

  • Posted Shameful Moose to byterock

    It is another shame day here in the Moose-pen

    I never like taking out code but that is the first thing I had to do today. So all the code changes from yesterday have been rolled back and I still have the same problem;

    
    Attribute (predicates) does not pa…
  • Posted Moose should of stayed in bed to byterock

    Still cleaning in here in the Moose-Pen

    Well was all ready to move onto the final documentation and distzila stage of Database::Accessor and then I ran into a few little tings when I reran the full test suite.

    First there was this annoying warning;

    ="prettypri…

  • Posted Still Cleaning Moose to byterock

    Still in mop up mode here in the Moose-Pen

    I finally found a way (well not a good one) to generate an even better error message to my end users. You are of course quite familiar with this type of message;


    Database::Accessor add_condition Error:…

  • Posted Just a little More Moose to byterock

    Its never stop improving day here in the Moose-Pen

    As I was cleaning things up today I found yet another little improvement I can do to my error messages. Right now when I have deeply buried bad item such as the 'names' in this $in_hash


    $in_has…

  • Posted No More Moose Loose Ends. to byterock

    Final final clean up day in the Moose-Pen

    Just a few quick things here in the Moose-Pen today. I want to make sure that my '_one_error' sub will return the same style of results no matter from where it is called and I want to make sure the 'DA_ALL_ERRORS' $ENV var is respected.

    I …

  • Posted The Moose Did it to byterock

    Its hold your head in shame smarty pants day here in the Moose pen.

    So here I am with a little 'mea culpa' for yesterday post. I had what you would call a real newbie flaw to to that I should of caught right away.

    Now it was not in the re-factoring or the implantation of the re-…

  • Posted le soleil roi d'orignal to byterock

    Its another re-factor day here in the Moose-Pen

    I left off yesterday with a little re factoring to do. I had essentially the same code for handling construction errors in Accessor.pm and in Types.pm. In any other object orientated language I ever worked with this would be rather a pain…

  • Commented on I'm fully covered
    as well as this one https://metacpan.org/pod/Pod::Coverage::TrustPod...
  • Commented on I'm fully covered
    Form the Pod::Coverage POD also_private also_private items are appended to the private list...
  • Posted Moose Loose Ends Part the XIII to byterock

    Its discovery day here in the Moose-Pen

    I was all ready to wrap up my 'new' constructor errors when I figured I better see what I get when I do something like this;


    $da->reset_conditions();
    $da->add_condition( {
    right …

  • Posted Moose Loose Ends Part the XII to byterock

    Well its fix one break everything day here in the Moose-Pen

    I thouhg it was just going to be one of those quick look how well things pass postette days today but I was dead wrong;

    I did a check in a a quick push and then ran the full test suite and got

    ="prett…

  • Posted Moose Loose Ends Part the XI to byterock

    Never say never day here in the Moose-pen

    Just when I though I had all the bugs out of my Database::Accessor I found a bunch more while finishing off tests case '42_new_validation.t'.

    Most of the bugs where with the 'links' attribute. My test for this attribute are a check to make …

  • Posted Moose Loose Ends Part the X to byterock

    Its make and mend day here in the Moose-Pen

    Now that I have my constructor single error working the way I like I figure I better go back and clean up my test cases and create a new test case just to check the error on 'new' construction.

    I am going to start with '30_view.t' as that…

  • Posted Moose Loose Ends Part the IX to byterock

    Another postette day here in the Moose-Pen

    I had only one little goal today and that is come up with a really nice single construction error message. After a good hour or so of mucking about I finally came up with;


    The following Attribute is req…

  • Posted Moose Loose Ends Part the VIII to byterock

    Its quick add in day here in the Moose-Pen

    Today I am going to add in another attribute called 'all_errors' a simple Boolean flag so my end user can either get a single error message of all the errors found or the 'MooseX::Constructor::AllErrors' object with all the errors when using the …

  • Posted Moose Loose Ends Part the Seventh to byterock

    Its very bad form day here in the Moose-pen

    Today I wanted to clean up one thing on construction error handling namely getting the correct number of errors back on my 'AllErrors' object.

    First a little house cleaning. The first thing I did today was create a new sub called '_new_m…

  • Posted Moose Loose Ends Part the Sixth to byterock

    Its dig deep an play day here in the Moose-Pen

    I my last post I figured out how to set up Database:Accessor to get the 'MooseX::Constructor::AllErrors' object in the 'around BUILDARGS' and then play with it…

  • Posted Moose Loose Ends V to byterock

    Still make errors pretty day here in the Moose-Pen.


    $in_hash = {
    view => {

Subscribe to feed Recent Actions from byterock

  • Ben Bullock commented on I'm fully covered

    That's ingenious, and if I was desperate to remove these things I would do that, but it seems to mean more complications in terms of having to maintain a bit of otherwise-useless documentation to fool the coverage system.

  • Aristotle commented on I'm fully covered
    In my opinion, marking private subroutines with a leading underscore is a de facto standard in the perl world. So, independently of the coverage issue, it would be a good thing to do.

    That would be a fair stance to take if we were talking about CPANTS, whose purpose is explicitly to be opinionated about best practice, because the proviso is that its score is only an indicator and not always correct or applicable – as it says, it measures kwalitee but not quality. In my view it is terrible for MetaCPAN to be dogmatic in the same way and it’s quite terrible to los…

  • Olaf Alders commented on I'm fully covered

    All of the coverage stats are generated by cpancover.com MetaCPAN is only returning the results provided by the cpancover API.

  • Aristotle commented on I'm fully covered

    It doesn’t make any difference to users whether MetaCPAN runs the coverage checking itself or endorses the data generated by another service. The weight given to the data by MetaCPAN is the same.

  • Ben Bullock commented on I'm fully covered

    Yes, metacpan is advertising these coverage results on their web site.

    For whatever reason, the coverage results are appearing inconsistently:

    https://metacpan.org/release/Table-Readable

    has no link but it's here:

    http://cpancover.com/latest/Table-Readable-0.03/index.html

    There are quite a lot of these glitches in the links, which don't seem to be formed correctly in many cases.

    Some of the coverage ratings seem to …

Subscribe to feed Responses to Comments from byterock

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is hosted by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.