Robust error handling #2

New Issue

hannaeko · 2020-04-29T21:51:40+02:00

hannaeko commented

2020-04-29 21:51:40 +02:00

Move to the almost non-existent error handling system to a somehow more robust:

Add context management to Parser struct (eg. line / char)
Use contextual string (string + context)
Use contextual error that refer to the input stream to show the syntax error
Provide mechanisms to map a parse error (like u32 or Ipv4Addr in RType::from_data) to a contextual error
Check for trailing parameters

Move to the almost non-existent error handling system to a somehow more robust: * [ ] Add context management to `Parser` struct (eg. line / char) * [ ] Use contextual string (string + context) * [ ] Use contextual error that refer to the input stream to show the syntax error * [ ] Provide mechanisms to map a parse error (like `u32` or `Ipv4Addr` in `RType::from_data`) to a contextual error * [ ] Check for trailing parameters

hannaeko added this to the DNS Zone 0.1 milestone 2020-04-29 21:55:33 +02:00

hannaeko referenced this issue

2020-04-30 02:21:09 +02:00

Create a Name for domain names #1

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: hannaeko/bind-conf#2