Re: [fpc-pascal] FPDoc - how to document overloaded functions?

2017-07-12 Thread Graeme Geldenhuys
On 2017-07-12 15:06, Michael Van Canneyt wrote: You can't. There are no provisions for this. I usually make the differences clear in the node. Thanks Michael. I've been playing around with fpdoc and trying a few things and then reviewing the results. Attached is the output I have thus far

Re: [fpc-pascal] Delete and Add for TBytes?

2017-07-12 Thread Sven Barth via fpc-pascal
Am 12.07.2017 16:08 schrieb "Bo Berglund" : > To remove Count processed bytes from the beginning: > > Buffer: AnsiString; > > Delete(Buffer, 1, Count) > or worse: > Buffer := Copy(Buffer, Count+1, Length(Buffer)); FPC trunk supports Delete() and Insert() on dynamic arrays (TBytes is merely a dynam

Re: [fpc-pascal] Delete and Add for TBytes?

2017-07-12 Thread Bo Berglund
On Wed, 12 Jul 2017 16:26:31 +0200 (CEST), Michael Van Canneyt wrote: >> Is it possible to overload Delete() so it can be called with TBytes as >> argument? > >It is. > OK, then I am doing it erroneously (Testing in Delphi XE5 at the moment, but trying to write it to be portable since the un

Re: [fpc-pascal] FPDoc - how to document overloaded functions?

2017-07-12 Thread Graeme Geldenhuys
On 2017-07-12 15:19, Graeme Geldenhuys wrote: ps #1: I haven't tried documenting function results yet, so not sure what FPDOC is going to do with that in this output. I had a look at documenting function results. There seems to be a bug (or place for improvement) in the HTML output. Even w

Re: [fpc-pascal] Delete and Add for TBytes?

2017-07-12 Thread Michael Van Canneyt
On Wed, 12 Jul 2017, Bo Berglund wrote: I would like to replace a buffer handling scheme in an old application (written in Delphi) where the buffer was originally of type string and later when unicode appeared changed to AnsiString. But AnsiString also causes potential headaches so I would li

[fpc-pascal] Delete and Add for TBytes?

2017-07-12 Thread Bo Berglund
I would like to replace a buffer handling scheme in an old application (written in Delphi) where the buffer was originally of type string and later when unicode appeared changed to AnsiString. But AnsiString also causes potential headaches so I would like to get rid of it altogether by using a TBy

Re: [fpc-pascal] FPDoc - how to document overloaded functions?

2017-07-12 Thread Michael Van Canneyt
On Wed, 12 Jul 2017, Graeme Geldenhuys wrote: Hi, How do you document overloaded functions? In this case I have overloaded functions that have different parameters (obviously), but also different result types. You can't. There are no provisions for this. I usually make the differences cl

Re: [fpc-pascal] FPDoc - how to document a function result?

2017-07-12 Thread Michael Van Canneyt
On Wed, 12 Jul 2017, Graeme Geldenhuys wrote: As the subject line says. Do I simply create a ELEMENT take with the function name and ".Result"? For example: This is the function result documentation. Or is there some other syntax? This is the correct syntax. Michael. ___

[fpc-pascal] FPDoc - how to document overloaded functions?

2017-07-12 Thread Graeme Geldenhuys
Hi, How do you document overloaded functions? In this case I have overloaded functions that have different parameters (obviously), but also different result types. I've been looking through the FPDoc PDF manual, but there is no explicit information on this subject. But then, I could be over

[fpc-pascal] FPDoc - how to document a function result?

2017-07-12 Thread Graeme Geldenhuys
As the subject line says. Do I simply create a ELEMENT take with the function name and ".Result"? For example: This is the function result documentation. Or is there some other syntax? Regards, Graeme -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourc