[fpc-devel] Problem documenting source code
After adding documentation for some items in the FPDoc Editor, I have problems running MakeSkel or FPDoc. Both report errors in the input file, which seem to be related to wrong or missing compiler options for that file. How can a documentation writer determine the required compiler options, so that the fpdoc tools can be made work? In former times[tm] I used make all -n in the source directory, to make the compiler options visible. But this approach fails now, the fpmake commandlines are not informative enough for that purpose. It may be a bad example (work in progress?), but I couldn't figure out the required compiler options for e.g. fcl-process/pipesipc.pp, in an attempt to create the skeletons for the fcl-process package. DoDi ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Problem documenting source code
On Fri, 17 Feb 2012, Hans-Peter Diettrich wrote: After adding documentation for some items in the FPDoc Editor, I have problems running MakeSkel or FPDoc. Both report errors in the input file, which seem to be related to wrong or missing compiler options for that file. How can a documentation writer determine the required compiler options, so that the fpdoc tools can be made work? In former times[tm] I used make all -n in the source directory, to make the compiler options visible. But this approach fails now, the fpmake commandlines are not informative enough for that purpose. It may be a bad example (work in progress?), but I couldn't figure out the required compiler options for e.g. fcl-process/pipesipc.pp, in an attempt to create the skeletons for the fcl-process package. Why would you want to do that ? These units are fully documented ? Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Problem documenting source code
michael.vancann...@wisa.be schrieb: It may be a bad example (work in progress?), but I couldn't figure out the required compiler options for e.g. fcl-process/pipesipc.pp, in an attempt to create the skeletons for the fcl-process package. Why would you want to do that ? I simply wanted to generate the skeletons for some FCL packages, based on --input-dir. The mentioned problems can occur with every source file. These units are fully documented ? In which version? DoDi ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] TMultiReadExclusiveWriteSynchronizer
Under Delphi if the TMultiReadExclusiveWriteSynchronizer writelock is held a read is not blocked if the ThreadID for the read is the same as the ThreadID for the write. Under FreePascal if writelock is held the read is always blocked regardless of ThreadID or anything else (implemented in the BeginRead method). I have some third party code that assumes that TMultiReadExclusiveWriteSynchronizer will work as it does in Delphi. I am wondering if the freepascal implementation is purposeful (read block even when in same thread is intentional) and I should talk to my third party vendor. Or if this is something that could/should be addressed in FreePascal. Thanks David Jenkins Scooter Software ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] TMultiReadExclusiveWriteSynchronizer
On 16 Feb 2012, at 23:56, David Jenkins wrote: Under Delphi if the TMultiReadExclusiveWriteSynchronizer writelock is held a read is not blocked if the ThreadID for the read is the same as the ThreadID for the write. Under FreePascal if writelock is held the read is always blocked regardless of ThreadID or anything else (implemented in the BeginRead method). I have some third party code that assumes that TMultiReadExclusiveWriteSynchronizer will work as it does in Delphi. I am wondering if the freepascal implementation is purposeful (read block even when in same thread is intentional) and I should talk to my third party vendor. Or if this is something that could/should be addressed in FreePascal. http://edn.embarcadero.com/article/28258 indicates that promoting read locks to write locks should work by design (which the current FPC implementation doesn't support either), so it's logical to assume that acquiring a read lock while you hold a write lock should also be possible. Feel free to file a bug report. Jonas___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] getting error, after publishing property
I have some code, and an error, that I can not explain (fpc 2.4.4 and 2.6) the base class defines public property Editor: TCustomSynEdit read GetEditor write SetEditor; in the inherited class, I can access Editor (of course I can) but I add published property Editor: TCustomSynEdit; in the inherited class and I get this error: B:\lazarus_latest\components\synedit\synpluginsyncroedit.pp(1099,53) Error: No member is provided to access property No Idea why (clean compile...) ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] getting error, after publishing property
Am 17.02.2012 16:15, schrieb Martin: I have some code, and an error, that I can not explain (fpc 2.4.4 and 2.6) the base class defines public property Editor: TCustomSynEdit read GetEditor write SetEditor; in the inherited class, I can access Editor (of course I can) but I add published property Editor: TCustomSynEdit; in the inherited class and I get this error: B:\lazarus_latest\components\synedit\synpluginsyncroedit.pp(1099,53) Error: No member is provided to access property No Idea why (clean compile...) Don't include the type of the property when increasing the visibility: published property Editor; This does not seem to be documented in the documentation though... (at least I haven't found it) Regards, Sven ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] getting error, after publishing property
Am 17.02.2012 16:23, schrieb Martin: On 17/02/2012 15:19, Sven Barth wrote: Am 17.02.2012 16:15, schrieb Martin: I have some code, and an error, that I can not explain (fpc 2.4.4 and 2.6) the base class defines public property Editor: TCustomSynEdit read GetEditor write SetEditor; in the inherited class, I can access Editor (of course I can) but I add published property Editor: TCustomSynEdit; in the inherited class and I get this error: B:\lazarus_latest\components\synedit\synpluginsyncroedit.pp(1099,53) Error: No member is provided to access property No Idea why (clean compile...) Don't include the type of the property when increasing the visibility: published property Editor; This does not seem to be documented in the documentation though... (at least I haven't found it) Ouch, ouch, ouch There are some days where we don't see the forest because of the trees ;) Regards, Sven ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
