The compiler and interpreter are independent from the desktop or toolkitĪnyway, so there is no need for developing KDE-specific versions of those. NET applications out there, primarily developed for Windows, and people will want to run those under Linux/Unix, with KDE/Qt widgets. NET, if I understand DotGNU correctly.Īnyway, KDE’s stand on the question is that “when we’ll be at a point where we need to add support for. For that reason, DotGNU looks much better to me than implementing Microsoft’s. I’m just not too fond of using a Microsoft solution for that, as “open” as they claim it to be. Is indeed appealing, and goes the right way in the long term. But the idea of cross-platform applications written in any programming language Written in either of those could be “pre-compiled” to native code, I suppose. However I realize that’s primarily a problem in browsers, native applications It can beĮither interpreted or compiled just in time, but none of those beat compiled code. I’m quite fond of Java, and C# seems to be the same kind of language, but speed has always been a problem with Java. NET is basically Microsoft’s reinvention of Java, with the possibility forĪny object-oriented language to be compiled into C# bytecode, which isn’t possible with Java itself. NET the Framework? Have you had a look to this new API yet? What are your thoughts of dotGNU and Ximian’s Mono?ĭavid Faure: From what I’ve seen – I admit I haven’t looked very much into the API though. But for the most common types of bugs (wrong code paths etc.) kdDebug() (the equivalent of printf or cout) and gdb do the job quite well □Ĥ. This is now available thanks to Julian Seward, who developed a GPL tool call valgrind.Īlthough still under development, this tool allows to find many non-obvious bugs in the code. What was missing for a long time was a memory debugger, to detect use of uninitialized or deleted memory etc., such as Purify provides. For advanced debugging such as memory leaks, kmtrace (in kdesdk) seems to do a good job too. On the subject of XEmacs, the KDE developers have been developing some macros (lisp code) that help developing C++ with it, this is available in kdesdk/scripts. In addition to the obvious compiler, debugger and text editor, Linux comes with pretty decent development tools such as XEmacs, vim, and kdevelop. How the Linux developers are coping when theyĪre in need to debug big projects like KDE or Gnome or Star Office? What tools do you use and how they compare to the Windows equivelant?ĭavid Faure: Those calling me that never told me □ Let’s talk about the development tools then. Windows enjoy the presense of some very advanced development tools, like the new VS.NET debugger or Purify/Quantify by Rational. Some people call you the “KDE Bug Crasher”. On the other hand, rumours have it that the gcc/ld developers are working on prelinking, which is something different, cleaner, faster, and stable.ģ. a quick change that doesn’t address the whole issue. I’m not aware of the details, but it seems objprelink is rather a “hack”, i.e. ![]() The objprelink method does not appear to be stable enough to work around this problem, it is known to be the reason for crashes in the Javascript engine and in KMail. ![]() Work is being done in that area, though not by the KDE developers themselves. ![]() The linker has indeed been identified as a cause for slowdown when starting C++ applications. Are the KDE people going to do something for the C++ loader problem in Linux, which results on slow KDE loading times? Is the object prelinked method ‘safe’, or work is being done to the loader itself, to add the needed functionality? KDE 3 is not a big architectural change (such as KDE 2.0 was), it is simply a continuation in the work on all applications, adding the features that the user requested, as well as improvingĢ. The IMAP support in KMail comes to mind too, as an important new feature, for those using IMAP. I’m not only saying this because I took part in the work on Javascript, but also because this was said to be the most important drawback of Konqueror in KDE 2 by many users. What is the best new advancement/feature found in KDE 3 in your opinion?ĭavid Faure: I think the most important improvement in KDE3 is the greatly improved Javascript and DHTML support in Konqueror. Read more for our interview with David regarding Konqueror, KDE object prelinking, Gnome and much more. David is also one of the people who have commited in bug squashing under KDE, especially after he got hired by Mandrake Software. His work can be found in KFM, Konqueror source code and he recently also picked up KOffice’s KWord development. David Faure is a well known developer in the KDE & Linux community.
0 Comments
Leave a Reply. |