From: silvioprog <sil...@gm...> - 2016-09-19 05:27:24
|
On Mon, Sep 19, 2016 at 2:01 AM, Michalis Kamburelis < mic...@gm...> wrote: > 2016-09-19 6:52 GMT+02:00 silvioprog <sil...@gm...>: > > > > Hello, > > > > Sometimes I use the RTL's exceptions like the EArgumentNilException, but > the PasDoc can't find it, returning: > > > > === begin error === > > > > Info[2]: Writing Docs for unit "XXX" > > Warning[1]: Could not resolve link "EArgumentNilException" (from > description of "YYY") > > > > === end error === > > > > However, I have own exceptions like the EArgumentEmptyException, and > PasDoc can find it. > > > > So, consider the following code: > > > > === begin code === > > > > ... > > public > > { Raises an exception indicating that a parameter is nil. > > > > @param(AName The name specified for the parameter.) > > @raises(EArgumentNilException Raised indicating the nil parameter.) > > } > > class procedure RaiseNilParam(const AName: string); static; inline; > > { Raises an exception indicating that a parameter is empty. > > > > @param(AName The name specified for the parameter.) > > @raises(EArgumentEmptyException Raised indicating the empty > parameter.) > > } > > ... > > > > === end code === > > > > it is going to generate the following documentation: > > > > > > > > besides the described error, notice that the font size of > EArgumentNilException is different from the EArgumentEmptyException. > > > > I don't want to PasDoc generate a link to RTL's EArgumentNilException, > but I need to keep the same font size of EArgumentEmptyException and avoid > to show that errors. > > > > This one is simply a bug:) The warning oops, thanks for clarify it, indeed I meant "How do I solve the WARNING". ^^' Warning[1]: Could not resolve link "EArgumentNilException" (from > description of "YYY") > > should be either removed or changed to an info like > > Info[2]: Could not resolve link "EArgumentNilException" (from > description of "YYY"), possibly this exception is defined in the RTL > > And the font should remain the same, indeed. > +1 > Looking at your screenshots, it seems that it's not about the > font-size, it's that EArgumentNilException is inside <code>..</code>, > and monospace fonts are traditionally rendered a little smaller by the > web browsers. In any case, the font of EArgumentNilException should > have the same style/everything as EArgumentEmptyException. > > I believe this was submitted already, but simply noone had time to fix > it. Contributions are welcome:) Let me know if you plan to attack it, > if not -- I may:) Great. I'm going to solve it ASAP ... :-) I've found extra spaces as showed in the picture below and I'm going to fix it too: [image: Inline image 1] when it was fixed: [image: Inline image 1] -- Silvio Clécio |