...is. Not that there's anything wrong with Wiki, I quite like it. :-) An anagram (Greek anagramma 'letters written anew', passive participle of ana- 'again' + gramma 'letter') is a type of word play, the result of rearranging the letters of a word or phrase to produce a new word or phrase, using all the original letters exactly once; e.g., Eleven plus two = Twelve plus one, A decimal point = I'm a dot in ...

... that is. Not that there's anything wrong with Wiki, I quite like it. :-) An anagram (Greek anagramma 'letters written anew', passive participle of ana- 'again' + gramma 'letter') is a type of word play, the result of rearranging the letters of a word or phrase to produce a new word or phrase, using all the original letters exactly once; e.g., Eleven plus two = Twelve plus one, A decimal point = I'm a dot in ...

..., that is. Not that there's anything wrong with Wiki, I quite like it. :-) An anagram (Greek anagramma 'letters written anew', passive participle of ana- 'again' + gramma 'letter') is a type of word play, the result of rearranging the letters of a word or phrase to produce a new word or phrase, using all the original letters exactly once; e.g., Eleven plus two = Twelve plus one, A decimal point = I'm a dot in place, ...

...that is. Not that there's anything wrong with Wiki, I quite like it. :-) An anagram (Greek anagramma 'letters written anew', passive participle of ana- 'again' + gramma 'letter') is a type of word play, the result of rearranging the letters of a word or phrase to produce a new word or phrase, using all the original letters exactly once; e.g., Eleven plus two = Twelve plus one, A decimal point = I'm a dot in place, Astronomers = ...

..., that is. Not that there's anything wrong with Wiki, I quite like it. :-) An anagram (Greek anagramma 'letters written anew', passive participle of ana- 'again' + gramma 'letter') is a type of word play, the result of rearranging the letters of a word or phrase to produce a new word or phrase, using all the original letters exactly once; e.g., Eleven plus two = Twelve plus one, A decimal point = I'm a dot in place, Astronomers = ...

...(0, 'blib/lib', 'blib/arch')" t/*.t t/altern......ok t/cjkrange....ok t/contract....ok t/hangtype....ok t/hangul......ok t/ignor.......ok t/illegal.....ok t/illegalp....ok t/index.......ok t/normal......ok t/override....ok t/rearrang....ok t/test........ok t/trailwt.....ok t/variable....ok t/version.....ok t/view........ok All tests successful. Files=17, Tests=873, 3 wallclock secs ( 2.65 cusr + 0.18 csys = 2.83 CPU) ...

...0, 'blib/lib', 'blib/arch')" t/*.t t/altern......ok t/cjkrange....ok t/contract....ok t/hangtype....ok t/hangul......ok t/ignor.......ok t/illegal.....ok t/illegalp....ok t/index.......ok t/normal......ok t/override....ok t/rearrang....ok t/test........ok t/trailwt.....ok t/variable....ok t/version.....ok t/view........ok All tests successful. Files=17, Tests=873, 4 wallclock secs ( 0.63 usr 0.04 sys + 2.68 cusr 0.30 csys =...

... type with pointer components which does not leak memory? To be more precise, the attached code, according to valgrind, leaks the memory allocated in tt_sum (which indeed seems reasonable to me). Is there a way to rearrange this code to avoid memory leaks? I have to add that 1) in general I can not switch to allocatable components 2) I think a FINAL procedure might solve the problem, but I wonder how many compilers ...

... that they were at least legally replaced, if not physically replaced. Testing code for copyright infringement isn't easy, though. If I find I=I+1 in two Fortran programs, that isn't much of an indicator that one was copied from the other. It might not be hard to write a program that would rearrange the code, change variable names, and otherwise obscure the original source. (Not the goal of most obfuscators.) -- glen

...type with pointer components which does not leak memory? To be more precise, the attached code, according to valgrind, leaks the memory allocated in tt_sum (which indeed seems reasonable to me). Is there a way to rearrange this code to avoid memory leaks? I have to add that 1) in general I can not switch to allocatable components 2) I think a FINAL procedure might solve the problem, but I wonder how many ...