Re: [Lazarus] Repository commit statistics. :-)
On Wed, Apr 15, 2009 at 22:37, Graeme Geldenhuys graemeg.li...@gmail.com wrote: Patches submitted to Mantis is applied by other users that have read/write access to the repository. So only those read/write users are shown. Yes, properly preserving author info in commits is another thing Git gets right, and Subversion does not. 2704 lazarus Hm, I wonder who he is ;-) -- Alexander S. Klenin ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] revision numbers of each SVN tag?
Doug Chamberlin schreef: What if, in response to a last-minute show stopper bug, the scheduled release was immediately superseded by another one with a higher release number? What would be the harm? It would make a lot of confusion. Do you really think that anyone likely to use these programs (FPC and Lazarus) would not be sympathetic and understanding about what happened and readily accommodate themselves to the fact that release x.y.z had a 1-day lifespan and that usable releases went from x.y.z to x.y.z+2? The x.y.z release would never released, it would have a minus 3 days life span. Note that this thread is talking about the situation, where the source in SVN has been tagged for the release builders, but no release has been made public. The x.y.z release would go from x.y.z to x.y.z+4 (no odd releases, see http://wiki.lazarus.freepascal.org/Version_Numbering) and you would have to explain the missing x.y.z+2, except that is visible in the svn history (I would delete the tag for the broken release from svn too). Especially if the explanation was readily available? Maybe. It's not like we are running out of release numbers or anything... Also, I don't buy the argument that doing this would delay the new release another 4 months. After all, it would be the exact same code being released under the move the tag scenario so no additional delay would be needed. Agreed. Vincent ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Repository commit statistics. :-)
Hm, I wonder who he is ;-) cat the developer?! :) ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Repository commit statistics. :-)
On Thu, Apr 16, 2009 at 7:53 AM, Alexander Klenin kle...@gmail.com wrote: Yes, properly preserving author info in commits is another thing Git gets right, and Subversion does not. Correct. Git can distinguish between the Author and Committer or a patch. Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Modified .po files after each build
Hi Jesus, You explanation makes sense. what to do?, simply do a diff with changed po files, somebody should apply the patch and everybody happy again. Please find the patch attached. Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ diff --git a/components/projecttemplates/languages/frmtemplatevariables.de.po b/components/projecttemplates/languages/frmtemplatevariables.de.po index f04ab28..874b3e0 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.de.po +++ b/components/projecttemplates/languages/frmtemplatevariables.de.po @@ -13,6 +13,10 @@ msgstr msgid Description msgstr Beschreibung +#: frmtemplatevariables.snoadditionalvars +msgid This project has no additional variables. +msgstr + #: frmtemplatevariables.svalue msgid Value msgstr Wert diff --git a/components/projecttemplates/languages/frmtemplatevariables.es.po b/components/projecttemplates/languages/frmtemplatevariables.es.po index b6d736d..61f7e42 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.es.po +++ b/components/projecttemplates/languages/frmtemplatevariables.es.po @@ -13,6 +13,10 @@ msgstr msgid Description msgstr Descripcion +#: frmtemplatevariables.snoadditionalvars +msgid This project has no additional variables. +msgstr + #: frmtemplatevariables.svalue msgid Value msgstr Valor diff --git a/components/projecttemplates/languages/frmtemplatevariables.fr.po b/components/projecttemplates/languages/frmtemplatevariables.fr.po index 02fc4d2..de84ed9 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.fr.po +++ b/components/projecttemplates/languages/frmtemplatevariables.fr.po @@ -13,6 +13,10 @@ msgstr msgid Description msgstr Description +#: frmtemplatevariables.snoadditionalvars +msgid This project has no additional variables. +msgstr + #: frmtemplatevariables.svalue msgid Value msgstr Valeur diff --git a/components/projecttemplates/languages/frmtemplatevariables.id.po b/components/projecttemplates/languages/frmtemplatevariables.id.po index 88941b9..8a4d1a9 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.id.po +++ b/components/projecttemplates/languages/frmtemplatevariables.id.po @@ -13,6 +13,10 @@ msgstr msgid Description msgstr Deskripsi +#: frmtemplatevariables.snoadditionalvars +msgid This project has no additional variables. +msgstr + #: frmtemplatevariables.svalue msgid Value msgstr Nilai diff --git a/components/projecttemplates/languages/frmtemplatevariables.it.po b/components/projecttemplates/languages/frmtemplatevariables.it.po index 043320a..4088838 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.it.po +++ b/components/projecttemplates/languages/frmtemplatevariables.it.po @@ -13,6 +13,10 @@ msgstr msgid Description msgstr Descrizione +#: frmtemplatevariables.snoadditionalvars +msgid This project has no additional variables. +msgstr + #: frmtemplatevariables.svalue msgid Value msgstr Valore diff --git a/components/projecttemplates/languages/frmtemplatevariables.lt.po b/components/projecttemplates/languages/frmtemplatevariables.lt.po index 4d29d4f..9d25ce3 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.lt.po +++ b/components/projecttemplates/languages/frmtemplatevariables.lt.po @@ -14,6 +14,10 @@ msgstr msgid Description msgstr Aprašas +#: frmtemplatevariables.snoadditionalvars +msgid This project has no additional variables. +msgstr + #: frmtemplatevariables.svalue msgid Value msgstr Vertė diff --git a/components/projecttemplates/languages/frmtemplatevariables.pb.po b/components/projecttemplates/languages/frmtemplatevariables.pb.po index 1e0519a..d0da0b3 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.pb.po +++ b/components/projecttemplates/languages/frmtemplatevariables.pb.po @@ -8,6 +8,10 @@ msgstr msgid Description msgstr Descricao +#: frmtemplatevariables.snoadditionalvars +msgid This project has no additional variables. +msgstr + #: frmtemplatevariables.svalue msgid Value msgstr Valor diff --git a/components/projecttemplates/languages/frmtemplatevariables.pl.po b/components/projecttemplates/languages/frmtemplatevariables.pl.po index 081baf2..521e22e 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.pl.po +++ b/components/projecttemplates/languages/frmtemplatevariables.pl.po @@ -15,6 +15,10 @@ msgstr msgid Description msgstr Opis +#: frmtemplatevariables.snoadditionalvars +msgid This project has no additional variables. +msgstr + #: frmtemplatevariables.svalue msgid Value msgstr Wartość diff --git a/components/projecttemplates/languages/frmtemplatevariables.po b/components/projecttemplates/languages/frmtemplatevariables.po index 5d1801b..24ba1de 100644 --- a/components/projecttemplates/languages/frmtemplatevariables.po +++
Re: [Lazarus] revision numbers of each SVN tag?
On Wed, Apr 15, 2009 at 07:26:58PM -0400, Doug Chamberlin wrote: What if, in response to a last-minute show stopper bug, the scheduled release was immediately superseded by another one with a higher release number? What would be the harm? FPC did that once 1.0.8 in 2003 or thereabouts. Afaik I deleted the FAQ item about it only an year ago. Never again. Also I've a bit the feeling that this whole discussion is a solution in search of a problem. There is no problem at all in the first place. ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] revision numbers of each SVN tag?
On Wed, Apr 15, 2009 at 10:14 PM, Hans-Peter Diettrich drdiettri...@aol.com wrote: Distinguish between distribution lines. My suggestion is for the repository itself. A tarball can contain the patched version, and can have other naming conventions. RPM packages frequently come with patches. etc. I am actually done chatting on this thread, but to reiterate your point. When last did you see a Windows OS being released and not have patches available in the first week of release. Even in open-source projects like Ubuntu. They day it gets released, there are updates to be downloaded. And with the Ubuntu LTS (Longe Term Support) versions they release point releases a few moths later - fixing even more bugs. Why can't FPC release patches ( or new .pp, .inc and .ppu files) for those unexpected show stoppers. It would save the release builders hours of time. Note, this is only mean for those critical unforeseen / show stopper issues. Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Why we chose Object Pascal instead
On Wed, Apr 15, 2009 at 4:12 PM, Felipe Monteiro de Carvalho wrote: And here is the best comment about it: I can't agree more... We have had this exact same issue in our company (before I arrived). They hired cheap (inexperienced) developers that caused havoc in the code. They make the GUI seem fine for a while, but underneath the design (if there actually was a design) is totally rubbish and unable to cope with new requirements. Hence the reason I was commissioned to do a total rewrite. Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] OT [Re: Why we chose Object Pascal instead]
On Wed, Apr 15, 2009 at 6:25 PM, Martin Friebe laza...@mfriebe.de wrote: Yeah, but where is the magazine: The programmer's inside ? Which compares individual programmers, and gives tips, whom to use for which purpose? You don't need a magazine for that. You simply need the right person to do the interview and give the candidates a skills test, relevant to the job, to do. This immediately gets rid of most rubbish candidates. Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] windowmanager interaction of lcl
On Thu, Apr 16, 2009 at 4:24 AM, Marc Santhoff m.santh...@web.de wrote: Hi, I'm still having trouble using GTK or GTK2 when running Window Maker (http://www.windowmaker.info/). Every time virtual desktops are switched lazarus itself and any application built with it are minimized. Is this a known bug? I believe this is reported in Mantis (or was). I know I mentioned it in the mailing list because it occured very frequent when using the KDE desktop, but not Gnome desktop. I think Mattias tried to look at it, but couldn't duplicate the issue - which makes fixing problems very hard. At the moment I'm back on Gnome, so I don't experience the issue any more using 0.9.27 (trunk). Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] revision numbers of each SVN tag?
Doug Chamberlin schrieb: What if, in response to a last-minute show stopper bug, the scheduled release was immediately superseded by another one with a higher release number? What would be the harm? Do you really think that anyone likely to use these programs (FPC and Lazarus) would not be sympathetic and understanding about what happened and readily accommodate themselves to the fact that release x.y.z had a 1-day lifespan and that usable releases went from x.y.z to x.y.z+2? Especially if the explanation was readily available? You missed the days when we skipped 1.0.8, right? It was an faq for years: where is version 1.0.8? It's not like we are running out of release numbers or anything... Also, I don't buy the argument that doing this would delay the new release another 4 months. After all, it would be the exact same code being released under the move the tag scenario so no additional delay would be needed. It requires at least another release candidate to get the version number at all placed right (compiler, makefiles, docs, readmes, installers ) and let it check by other people and to test if all defines are still correct. And the more release candidates you do, the more tired builders get, so times spans get longer and longer with every release candidate. ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Repository commit statistics. :-)
Alexander Klenin schrieb: On Wed, Apr 15, 2009 at 22:37, Graeme Geldenhuys graemeg.li...@gmail.com wrote: Patches submitted to Mantis is applied by other users that have read/write access to the repository. So only those read/write users are shown. Yes, properly preserving author info in commits is another thing Git gets right, and Subversion does not. Who needs it? My sat nav can also plan routes for trucks but it is not the reason why I use it. The real name of a submitter goes into the log, the person responsible for the commit is known by subversion. ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Repository commit statistics. :-)
On Thu, Apr 16, 2009 at 9:21 AM, Florian Klaempfl flor...@freepascal.org wrote: The real name of a submitter goes into the log, the person responsible for the commit is known by subversion. So you do the same thing but manually - that git does automatically for you (and makes it an official feature). Who knows what statistics developers want in the future? :-) Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] 32 bit application on 64 bit
Dear all,
I developed a console application with lazarus, I compiled it on a 32
bit machine (Linux).
Actually I received an e-mail by one of the final user that is trying to
run it on a 64 bit machine (Red Hat Enterprise Linux 5.x (5.1)). The
application crash with the message reported at the end of this e-mail.
I know that there are libraries for compatibility but I never used a 64
bit machine and I don't know how to help the final user.
I would like to know if my lazarus 32 bit application can run on a 64
bit machine and if someone of you can suggest me where the 32/64 bit
libraries can be found.
Many thanks,
Andrea
exception at 080C610E:
Access violation.
strace shows an segfault
...
...
brk(0x82cb000) = 0x82cb000
socket(PF_FILE, SOCK_STREAM, 0) = 3
fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0
connect(3, {sa_family=AF_FILE, path=/var/run/nscd/socket}, 110) = 0
poll([{fd=3, events=POLLOUT|POLLERR|POLLHUP, revents=POLLOUT}], 1, 5000) = 1
send(3, \2\0\0\0\v\0\0\0\7\0\0\0passwd\0, 19, MSG_NOSIGNAL) = 19
poll([{fd=3, events=POLLIN|POLLERR|POLLHUP, revents=POLLIN|POLLHUP}], 1, 5000)
= 1
recvmsg(3, {msg_name(-5820488)=NULL, msg_iov(68719476736)=[?] 0x10ffa72fa8,
msg_controllen=18421743979612602372, msg_control=0x10001,
msg_flags=MSG_OOB|MSG_DONTROUTE|MSG_PEEK}, 0) = 7
fstat64(4, {st_mode=S_IFREG|0600, st_size=217016, ...}) = 0
pread64
(4, \1\0\0\0h\0\0\0\256V\1\0\1\0\0\0\200\210tI\0\0\0\0\323\0\0\0\0L\3\0...,
104, 0) = 104
mmap2(NULL, 217016, PROT_READ, MAP_SHARED, 4, 0x34fb8) = 0xf7eb5000
close(4)= 0
close(3)= 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigprocmask(SIG_UNBLOCK, [SEGV], NULL, 8) = 0
write(1, exception at 080C610E:\nAccess vi..., 41exception at 080C610E:
Access violation.
) = 41
munmap(0xf7f32000, 32768) = 0
munmap(0xf7fdd000, 32768) = 0
munmap(0xf7f6a000, 262144) = 0
munmap(0xf7fed000, 32768) = 0
munmap(0xf7f62000, 32768) = 0
munmap(0xf7fe5000, 32768) = 0
munmap(0xf7f02000, 32768) = 0
munmap(0xf7ef2000, 32768) = 0
munmap(0xf7f22000, 32768) = 0
munmap(0xf7f12000, 32768) = 0
munmap(0xf7f1a000, 32768) = 0
munmap(0xf7ff5000, 32768) = 0
munmap(0xf7f3a000, 32768) = 0
munmap(0xf7f2a000, 32768) = 0
munmap(0xf7f52000, 32768) = 0
munmap(0xf7f42000, 32768) = 0
munmap(0xf7f4a000, 32768) = 0
munmap(0xf7eea000, 32768) = 0
munmap(0xf7efa000, 32768) = 0
munmap(0xf7f0a000, 32768) = 0
exit_group(0) = ?
___
Lazarus mailing list
Lazarus@lazarus.freepascal.org
http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] How to change ListView item background color (in report style)??
I need something like this http://www.delphidabbler.com/img/articles/16-3.gif example Drawing rows in alternating colors http://www.delphidabbler.com/articles?article=16part=1#eg2 i tried code in Listing 4 but did not work... How do I do that in Lazarus ?? JB -- Tysiace zabawnych wierszyków.Dodaj swoj Sprawdz http://link.interia.pl/f1fcd ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Repository commit statistics. :-)
2009/4/16 Graeme Geldenhuys graemeg.li...@gmail.com: On Thu, Apr 16, 2009 at 9:21 AM, Florian Klaempfl flor...@freepascal.org wrote: The real name of a submitter goes into the log, the person responsible for the commit is known by subversion. So you do the same thing but manually - that git does automatically for you (and makes it an official feature). Who knows what statistics developers want in the future? :-) i think what he means is that you can find out which developer has made which change (svn blame). that's useful. i'm sure git can do the same. i can't see the point of shortlog -n, except something you would present at a management meeting to prove that you're the busiest developer. henry ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] revision numbers of each SVN tag?
Op donderdag 16-04-2009 om 08:49 uur [tijdzone +0200], schreef Graeme Geldenhuys: On Wed, Apr 15, 2009 at 10:14 PM, Hans-Peter Diettrich drdiettri...@aol.com wrote: Distinguish between distribution lines. My suggestion is for the repository itself. A tarball can contain the patched version, and can have other naming conventions. RPM packages frequently come with patches. etc. I am actually done chatting on this thread, but to reiterate your point. When last did you see a Windows OS being released and not have patches available in the first week of release. Even in open-source projects like Ubuntu. They day it gets released, there are updates to be downloaded. And with the Ubuntu LTS (Longe Term Support) versions they release point releases a few moths later - fixing even more bugs. Well, you don't have any experience in building linux-distribution releases also, that is clear. For distributions the same thing holds as for us: if a show-stopper occurs, the release is delayed. Last example is the release of Fedora 11 beta. It was delayed 2 weeks because of some show-stoppers. (2 weeks is very long, and believe me: nobody was happy with it) But the point is that distributions only find issues 'show-stoppers' when the files concerned are on the cd's. And if they contain bugs in the installer, or security issues while installing Fedora. Thus: problems which may arrise before the patch-and-update mechanism is in place. (This was also the problem in the latest fpc release: it was only harmfull the first time you would run the installation-utility) Distributions handle things like these exactly as how we do. Unimportant things can be done in patches. Why can't FPC release patches ( or new .pp, .inc and .ppu files) for those unexpected show stoppers. It would save the release builders hours of time. Note, this is only mean for those critical unforeseen / show stopper issues. Well, that's one of the reasons we made fppkg. But that's not something you do in a few weeks... Joost. ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Why we chose Object Pascal instead
Graeme Geldenhuys schrieb: I can't agree more... We have had this exact same issue in our company (before I arrived). They hired cheap (inexperienced) developers that caused havoc in the code. They make the GUI seem fine for a while, but underneath the design (if there actually was a design) is totally rubbish and unable to cope with new requirements. Hence the reason I was commissioned to do a total rewrite. That's why neither Cobol nor VB will ever die: they make secure long-term jobs DoDi ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Repository commit statistics. :-)
Graeme Geldenhuys schrieb: On Thu, Apr 16, 2009 at 9:21 AM, Florian Klaempfl flor...@freepascal.org wrote: The real name of a submitter goes into the log, the person responsible for the commit is known by subversion. So you do the same thing but manually - that git does automatically for you (and makes it an official feature). The bad thing is: if the original patch was made by some who setup git wrongly (which is rather likely for someone using git seldomly, e.g. I enter always a random name and email address when setting up an account on a machine), you don't have a real name of the submitter. Further, I don't add the email address of the submitter to the log on purpose to make life for spammers harder. ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Why we chose Object Pascal instead
On Thu, Apr 16, 2009 at 11:25 AM, Hans-Peter Diettrich drdiettri...@aol.com wrote: That's why neither Cobol nor VB will ever die: they make secure long-term jobs In some twisted way that is probably true. :-) Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] [?? Probable Spam] Re: function StabBackTraceStr(addr:Pointer):shortstring; - problem with subsequent back traces
Sergei Gorelkin pisze: Bogusław Brandys пишет: There is a problem with this function. To avoid recursion there is a hack there to point BackTraceStrFunc to system implementation (which only shows addresses in hex).Long back trace which mostly ends with incorrect frame address as I suppose (OpenStabs is returning false for nil address) - thus function pointer is not returned back to lineinfo stabs processing method and next back trace contains only addresses . Right you are. However, many backtraces *start* with an invalid frame: e.g. when you call a virtual method of an object that is already destroyed, you'll likely end up at a random address. I attached my proposition of patch here : http://bugs.freepascal.org/view.php?id=13518 and here (only windows) for external debug files (.dbg) : http://bugs.freepascal.org/view.php?id=13499 Do you have testcases for testing such invalid frames like in example above and for testing recursion ? Would be great if someone looked at proposed solution and checked under unix,win64 and other supported systems. This problem is minor if program crashes with exception and stack trace but in other cases , like in bigger program (any Lazarus ones) , ONLY first back trace has useful information (source,line number) attached to it. That eliminates any useful logging like multilog for example. And nobody really is able to know correct stack frames length before calling any of such functions to obtain back trace (that would resolve problem). How we could fix it ? Is this recursion still a subject here ? I fixed one of the causes recently (see exeinfo.pp, rev.12802), but that wasn't enough. In general, code of lineinfo, lnfodwrf and exeinfo has to be checked very carefully to make sure it would not crash at any circumstances. Including possibly unknown/corrupted state of the RTL in case when backtrace is called due to a crash. I have one idea, probably not perfect. How about a function to initialize BackTraceStrFunc : TBackTraceStrFunc; The only way now is to set : BackTraceStrFunc := @SysBackTraceStr; (displays only hex of addresses) Something generic is needed, able to set to StabBackTraceStr if lineinfo unit (option -gl) is used and only to SysBackTraceStr in other case. It might be used also to set to user defined function. That way in any such functions in lcl (DumpExceptionBackTrace,GetStackTrace) or external package (like multilog), we could initialize BackTraceStrFunc to point again to correct function before obtaining stack trace. For me, it looks simpler and better to restore BackTraceStrFunc unconditionally at the end of StabsBackTraceFunc/DwarfBackTraceFunc. Or even better, have it set to stub only for calling GetLineInfo. Regards, Sergei That's what I did among other changes. Regards Bogusław ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] anouncements about commerical application
hello the questions: Is it correct to make an anouncements about commercial (closed-source) applications created using Lazarus and FreePascal on the mailling list and/or at the Lazaruses forum (http://forum.lazarus.freepascal.org/index.php?board=19.0)? I've seen some anouncements about a commercial application on the list, but i don't remember to see any on the Lazarus forum. thanks, dmitry ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] anouncements about commerical application
To me it is correct. It'll also help spread the word about Lazarus and FPC's quality for creating real-world applications. Leonardo M. Ramé Griensu S.A. - Medical IT Córdoba Tel.: 0351 - 4247979 dmitry boyarintsev escribió: hello the questions: Is it correct to make an anouncements about commercial (closed-source) applications created using Lazarus and FreePascal on the mailling list and/or at the Lazaruses forum (http://forum.lazarus.freepascal.org/index.php?board=19.0)? I've seen some anouncements about a commercial application on the list, but i don't remember to see any on the Lazarus forum. thanks, dmitry ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] anouncements about commerical application
Yes, it is. They are interresting to show that big projects can be developed with Lazarus. -- Felipe Monteiro de Carvalho ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] Why we chose Object Pascal instead
Hans-Peter Diettrich wrote: Graeme Geldenhuys schrieb: I can't agree more... We have had this exact same issue in our company (before I arrived). They hired cheap (inexperienced) developers that caused havoc in the code. They make the GUI seem fine for a while, but underneath the design (if there actually was a design) is totally rubbish and unable to cope with new requirements. Hence the reason I was commissioned to do a total rewrite. That's why neither Cobol nor VB will ever die: they make secure long-term jobs that's also why real coders do not comment their source code ;) -- NOTE: NEW EMAIL ADDRESS!! _\/ (@@) Waldo Kitty, Waldo's Place USA __ooO_( )_Ooo_ telnet://bbs.wpusa.dynip.com _|_|_|_|_|_|_ http://www.wpusa.dynip.com |_|_|_|_|_| ftp://ftp.wpusa.dynip.com _|_Eat_SPAM_to_email_me!_YUM!__|_ wkitty42 -at- windstream.net ___ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus
