[fpc-pascal] FreeBSD binary compatibility
I was trying out a couple of examples and figured I would try to see how portable the binaries were. Compiled a trivial program in FreeBSD 6.2 Stable and copied it to a 4.9 machine. The binary worked. Is that commontly the case? ie the binaries can be run accross different FreeBSD versions? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] RTL documentation
Is there a separate list for documentation? In particular I was wondering if there was any interest in adding some examples to the Socket section in the RTL documentation. As I am getting re-familiarized with pascal I am finding examples in the RTL library to be most helpfull. However when I got to the sockets section I have not yet seen any samples. If there is any interest I would be happy to help out.. as I learn it myself. :-) Already found this link that may be of help www.bastisoft.de/pascal/pasinet.html It was mentioned in some recent emails in the list. By the way.. thanks to the team/person who has put all the docs together. They are most helpfull. Downloaded a few of the PDFs and reading up on them. I must say that I am happy I am coming back to Pascal. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Usage of TInterfacedObject. Automatic release?
Luiz Americo, This was my first idea. And now gains force again. The problem is that the bug can not be isolated easily. Another option is that there's a mem leak in delphi also. Does some one know how to trace a mem leak in delphi? Use FastMM with FullDebugOptions []s Cesar Romero ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Usage of TInterfacedObject. Automatic release?
Marc Weustink wrote: Luiz Americo Pereira Camara wrote: Cesar Romero wrote: Luiz Americo, Anyway, calling manually _Release avoid the leak and i will stay with it for now (I hope did not break anything). It can work for that case, but I think that is not a good ideia. If you are using a TInterfacedObject descendant, it will call the _Release when out of context, so in that especific case seems to never go out of context, and then you _realease call works, but in other place it can go out of context before, and the you will have others AV. - As Joao suggest, the best way is create a weak reference, where when 2 objects need to reference each other one should use Pointer to hold one reference - Avoid circular reference The problem here is that i'm using a third party design. And the code complexity allied with my inexperience with interfaces/COM makes the chance of breaking things big. Anyway i did not find, with my limitations, any circular references between interfaces. Exists a circular reference but is between an Interface (IVTDragManager) and a TVirtualTreeView(TCustomControl) already used as a weak reference (TObject). The design is more or less the following: TBaseVirtualTree holds a reference to a IVTDragManager. TVTDragManager (IVTDragManager) holds a reference to TBaseVirtualTree stored in a TObject field TVTDragManager also holds reference for IDataObject (TVTDataObject) and IDropTargetHelper (returned by a win32 call) TVTDataObject holds a reference to TBaseVirtualTree as a TObject There are two circular references: TVTDragManager <-> TBaseVirtualTree TBaseVirtualTree <-> TVTDragManager > TVTDataObject > TBaseVirtualTree Circular references of object is not the problem, you should look at circular references of interfaces. As i explained i did not found interface circular references. (Although does not mean it does not exists ;-)) However, I don't expect that this is the case for the virtualtree. THat you need a _release for fpc and not for delphi sounds like a bug in fpc. (only where) This was my first idea. And now gains force again. The problem is that the bug can not be isolated easily. Another option is that there's a mem leak in delphi also. Does some one know how to trace a mem leak in delphi? Luiz ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Usage of TInterfacedObject. Automatic release?
Graeme Geldenhuys wrote: The virtual treeview has already been ported twice by two different people. Any particular reason you are doing it again? See the link for one of the ports... http://tinyurl.com/2uxewm The other one was based on a newer version of VT, but I don't think the port was 100% complete yet. See https://luipack.bountysource.com/wiki/virtualtreeview . There you will find the port roadmap and a link for the reasons of a new port. The new port is not complete yet. But fully working both in win32 and gtk (1 and 2). Most of the bugs of the first port were fixed (horizontal scrolling, checkboxes images, editors position, header resize) and even a delphi bug was fixed. Luiz ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Usage of TInterfacedObject. Automatic release?
On 5/26/07, Luiz Americo Pereira Camara <[EMAIL PROTECTED]> wrote: I don't have any experience with interfaces but is quite possible that this is the case. The component i'm porting is the TVirtualTreeView that uses extensively interfaces/COM and this part of the code is a bit complex. The virtual treeview has already been ported twice by two different people. Any particular reason you are doing it again? See the link for one of the ports... http://tinyurl.com/2uxewm The other one was based on a newer version of VT, but I don't think the port was 100% complete yet. -- Graeme Geldenhuys General error, hit any user to continue. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Re: Windows CE emulator and console
Hello, When you run your emulateur, you give the repertorie witch is shared between lazarus (compile exe) and the emulator. ex : "C:\Program Files\Microsoft Device Emulator\1.0\DeviceEmulator.exe" pocketpc.nb0 /skin Pocket_PC.xml /memsize 128 /sharedfolder C:\LzProjet\man\ Here i lunch the emulator with image Os Wince : pocketpc.nb0 (same directorie as exe of emulator) Picture of the pocket Pc model : /skin pocket_pc.xml (one in the emulator install) size of Ram : /memsize 128 (for exemple 128 meg) directorie share : /sharefolder C:\LzProjet\man\ ( my lazarus project is, and for exemple with an test.exe You compile under lazarus to have a test.exe Under the emulator, you lunch "file explorator" (programs), and you go to "Sd card", your Sd Card is the shared directorie. You click on test.exe. You had to stop the run each time before recompile, or the file will be busy (test.exe used by emulator). The (X) on the rigth of the windows don't stop the run on pocket pc, you must stop the run by a button witch close the main window. (or you stop the process under system / memory / stop process. I also access to the web under the emulator, test that in a first time. bye. Patrick from France, excuse me for my english.. 2007/5/26, Felipe Monteiro de Carvalho <[EMAIL PROTECTED]>: On 5/25/07, patrick feillant <[EMAIL PROTECTED]> wrote: > I use Microsoft Device emulator standalone, which emule pocket Pc , it is > very easy. How do you run your apps on the emulator? > But is not a new emulator ? Yes, it' s the same emulator as before, but what I ment is that they updated the operating system, and on the new one the consoles don' t work. -- Felipe Monteiro de Carvalho ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
