#77 Clarifications for parsing interfaces

[Markus Elfring]

The class "fastformat::format_parsing_exception" is scantily described.
http://www.fastformat.org/documentation/classfastformat_1_1format__parsing__exception.html

Your article "C++ and format_iterator" (from 2010-06-02) explains some details.
http://www.drdobbs.com/cpp/225300162

I miss descriptions about interfaces and (base) classes and their relationships for a key feature like parsing/data analysis.
Would you like to extend your published explanations?

[Matt Wilson]

Markus

Would you mind starting a thread on the Open Discusion forum - https://sourceforge.net/projects/fastformat/forums/forum/612781 - so we can explore this issue more easily?

Thanks

Matt

[Markus Elfring]

Thanks for your response.

Why do you prefer the forum user interface over this issue tracker?

[Matt Wilson]

Hi Markus

Mainly it's because the forums allow code formatting, hyperlinks, and so on.

Also, I tend to think of the Feature Request tracker as something to use when the idea is fully formed. (I'm not saying these ideas are not well formed in your mind, but I think I'll need more explanation to understand precisely what you're after in each case.)

Once things are discussed through, at that point a tracker entry here will be appropriate.

Hope that's ok. :-)

Matt

[Markus Elfring]

> Mainly it's because the forums allow code formatting, hyperlinks, and so on.

I find such features also nice if they are supported by an issue tracker.

> Also, I tend to think of the Feature Request tracker as something to use
> when the idea is fully formed.

That's not my habit. ;-)

> Hope that's ok.

Yes, of course. - We have just got different personal preferences for issue tracking tools.

Would you like to continue the discussion for my clarification request by the other interface?
https://sourceforge.net/projects/fastformat/forums/forum/612781/topic/4065825