Some small memory leaks ..

Hi, For writing my diploma thesis, I remembered the lyx project .. and am now using it ;-) Maybe I'll have some time to notice usability issues or bugs and fix them; what I've seen so far is, that lyx developed great in the last couple of years, notably the use of STL containers makes the code

Exceptions .. ?

Hi, Sorry if I ask dumb questions. I've seen, that the code is compiled with -fno-exceptions. Is this, because some systems/compilers do not yet support exceptions well ? I think that exceptions can help make code better readable and I'd suggest using them if possible (since programmers tend to

Re: Some small memory leaks ..

HI, On 7 Mar 2001, Lars Gullik Bjnnes wrote: LGBn| Can you redo this now with current cvs? I belive that most of them LGBn| should be fixed now. (I know there are some I did not fix...) Starting and stopping an empty lyx now causes only 852 Bytes memory leak; The last thing is interesting:

POSIX option handling

Hi, In a search for a small task to be done besides my other assignments, I had a look at the current option handling and re-implemented it more versatile in a way, that is handles long options more flexible (understands GNU-like long options like --dbg or old (non-POSIX conformant) options

Re: POSIX option handling

Hi, On 8 Mar 2001, Lars Gullik Bjnnes wrote: LGBn| Did you have a look at the command line parser proposed for use in LGBn| Boost:: ? Err .. no .. is there an URL I can look at ? ciao, -hen

Re: Some small memory leaks ..

HI, update: Lars, looks good now in current CVS - the only leak left, as you noted is the following - and yes, it is not easy to fix. | #-- Leak: counted 19x / total Size: 224 | 0x80c09f3 is in flyx_ident_extract(char const *) (lyx_gui_misc.C:209). | 208 | 209 char * sb =

Re: Some small memory leaks ..

Hi, On 8 Mar 2001, Jean-Marc Lasgouttes wrote: | And if you load a file? ~/bin/LeakCheck ./src/lyx -x lyx-quit /usr/share/lyx/doc/UserGuide.lyx yields, ahem, several (425) leaks at 39 different places (total 25716 Bytes), but only in the formula stuff which is currenly worked on, so expected

Re: Some small memory leaks ..

Hi, Update.. On Thu, 8 Mar 2001, Henner Zeller wrote: HZ| yields, ahem, several (425) leaks at 39 different places (total 25716 HZ| Bytes), for overall 2'272'211 allocations in LyX and maximum memory used in parallel 760 kBytes this is a not too bad ratio :-/ ciao, -hen

Re: style question

Hi, On Fri, 9 Mar 2001, John Levon wrote: JL| Why are people using : JL| JL| (*iterator).whatever JL| JL| rather than : JL| JL| iterator-whatever the operator- requires to return a pointer .. which is sometimes not possible to implement in an iterator, specifically, if the iterator

Re: The LyX licence

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Angus, | please excuse the personal email, but I'm trying to do something about | the messy state of the LyX licence and need your help. Thank you for cleaning up the license situation. | In light of all this, I'm asking whether I can have

Indentation (was: [PATCH] Fix memory leaks)

Hi, two short remarks; I usually put these lines in every file I write /* Emacs: * Local variables: * c-basic-offset: 8 * End: * vi:set tabstop=8 shiftwidth=8 nowrap: */ which is understood by emacs and vim so these editors are switched to the 'correct' indentation style automatically

Re: Indentation (was: [PATCH] Fix memory leaks)

HI, LGBn| [ Emacs - .. Lots Of Irritating Single Parenthesis [LISP]] LGBn| and since this is my setup it is also defining the coding style we use LGBn| in LyX. (more or less) LGBn| LGBn| c-basic-offset is only part of it. .. but the most annoying if there are mixed indentation styles. I

RE: Indentation (was: [PATCH] Fix memory leaks)

Hi, On Wed, 4 Apr 2001, Juergen Vigna wrote: JV| /* Emacs: JV| * Local variables: JV| * c-basic-offset: 8 JV| * End: JV| * vi:set tabstop=8 shiftwidth=8 nowrap: JV| */ JV| JV| Where at the very beginning or at the end? (I've read you have to JV| put this in the first line of the file

Re: The LyX licence

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Angus, | please excuse the personal email, but I'm trying to do something about | the messy state of the LyX licence and need your help. Thank you for cleaning up the license situation. | In light of all this, I'm asking whether I can have

Some small memory leaks ..

Hi, For writing my diploma thesis, I remembered the lyx project .. and am now using it ;-) Maybe I'll have some time to notice usability issues or bugs and fix them; what I've seen so far is, that lyx developed great in the last couple of years, notably the use of STL containers makes the code

Exceptions .. ?

Hi, Sorry if I ask dumb questions. I've seen, that the code is compiled with -fno-exceptions. Is this, because some systems/compilers do not yet support exceptions well ? I think that exceptions can help make code better readable and I'd suggest using them if possible (since programmers tend to

Re: Some small memory leaks ..

HI, On 7 Mar 2001, Lars Gullik Bjønnes wrote: LGBn| Can you redo this now with current cvs? I belive that most of them LGBn| should be fixed now. (I know there are some I did not fix...) Starting and stopping an empty lyx now causes only 852 Bytes memory leak; The last thing is interesting:

POSIX option handling

Hi, In a search for a small task to be done besides my other assignments, I had a look at the current option handling and re-implemented it more versatile in a way, that is handles long options more flexible (understands GNU-like long options like --dbg or old (non-POSIX conformant) options

Re: POSIX option handling

Hi, On 8 Mar 2001, Lars Gullik Bjønnes wrote: LGBn| Did you have a look at the command line parser proposed for use in LGBn| Boost:: ? Err .. no .. is there an URL I can look at ? ciao, -hen

Re: Some small memory leaks ..

HI, update: Lars, looks good now in current CVS - the only leak left, as you noted is the following - and yes, it is not easy to fix. | #-- Leak: counted 19x / total Size: 224 | 0x80c09f3 is in flyx_ident_extract(char const *) (lyx_gui_misc.C:209). | 208 | 209 char * sb =

Re: Some small memory leaks ..

Hi, On 8 Mar 2001, Jean-Marc Lasgouttes wrote: | And if you load a file? ~/bin/LeakCheck ./src/lyx -x lyx-quit /usr/share/lyx/doc/UserGuide.lyx yields, ahem, several (425) leaks at 39 different places (total 25716 Bytes), but only in the formula stuff which is currenly worked on, so expected

Re: Some small memory leaks ..

Hi, Update.. On Thu, 8 Mar 2001, Henner Zeller wrote: HZ| yields, ahem, several (425) leaks at 39 different places (total 25716 HZ| Bytes), for overall 2'272'211 allocations in LyX and maximum memory used in parallel 760 kBytes this is a not too bad ratio :-/ ciao, -hen

Re: style question

Hi, On Fri, 9 Mar 2001, John Levon wrote: JL| Why are people using : JL| JL| (*iterator).whatever JL| JL| rather than : JL| JL| iterator->whatever the operator-> requires to return a pointer .. which is sometimes not possible to implement in an iterator, specifically, if the iterator

Indentation (was: [PATCH] Fix memory leaks)

Hi, two short remarks; I usually put these lines in every file I write /* Emacs: * Local variables: * c-basic-offset: 8 * End: * vi:set tabstop=8 shiftwidth=8 nowrap: */ which is understood by emacs and vim so these editors are switched to the 'correct' indentation style automatically

Re: Indentation (was: [PATCH] Fix memory leaks)

HI, LGBn| [ Emacs - .. Lots Of Irritating Single Parenthesis [LISP]] LGBn| and since this is my setup it is also defining the coding style we use LGBn| in LyX. (more or less) LGBn| LGBn| c-basic-offset is only part of it. .. but the most annoying if there are mixed indentation styles. I

RE: Indentation (was: [PATCH] Fix memory leaks)

Hi, On Wed, 4 Apr 2001, Juergen Vigna wrote: JV| > /* Emacs: JV| > * Local variables: JV| > * c-basic-offset: 8 JV| > * End: JV| > * vi:set tabstop=8 shiftwidth=8 nowrap: JV| > */ JV| JV| Where at the very beginning or at the end? (I've read you have to JV| put this in the first line of