taskLibreDWG - Tasks: task #9858, Clean debugging messages and...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #9858: Clean debugging messages and return error codes

Submitter:  Rodrigo Rodrigues da Silva <pitanga>
Submitted:  Wed 04 Nov 2009 03:44:52 AM UTC
   
 
Should Start On:  Wed 04 Nov 2009 02:00:00 AM UTC Should be Finished on:  Wed 04 Nov 2009 02:00:00 AM UTC
Category:  None Priority:  5 - Normal
Status:  Done Privacy:  Public
Assigned to:  reini_urban Percent Complete:  100%
Open/Closed:  Closed Effort:  0.00

Fri 08 Jun 2018 05:27:10 PM UTC, comment #2: 

I've added now error codes to the API, the sample programs and the documentation. For now in the errors branch.

Errors are sorted by severity, and stored as bitmask, but not the count of each error.

There are harmless errors and critical errors.
https://github.com/LibreDWG/libredwg/commits/errors

Reini Urban <reini_urban>
Group administrator
Wed 25 Apr 2018 11:16:37 AM UTC, comment #1: 

I agree.

Currently we enforce printing error messages on the WARN and ERROR level,
and I've added more error status returns.

What needs to be added are some symbolic error status numbers into dwg.h
or maybe even an enum, and use them instead.

Out of memory, out of bounds, failed to read class, failed to write class, crc error and more of such.

Reini Urban <reini_urban>
Group administrator
Wed 04 Nov 2009 03:44:52 AM UTC, original submission:  

As suggested by Karl on 2009-10-19

"All the messages in LibreDWG that I looked at are either debugging (which is fine, of course) or exceptional error cases.  Is that right? As a library, it seems it would be normal to never output anything, just return error codes?"

Rodrigo Rodrigues da Silva <pitanga>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by reini_urban (Posted a comment)
  • -email is unavailable- added by pitanga (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-06-08 reini_urban StatusIn Progress Done
        Percent Complete20% 100%
        Open/ClosedOpen Closed
    2018-04-25 reini_urban Assigned topitanga reini_urban
    2010-01-20 pitanga Priority1 - Later 5 - Normal
        StatusNone In Progress
        Percent Complete0% 20%
        Assigned toNone pitanga

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code