From kdevelop-devel Mon Oct 01 17:28:36 2007 From: Jens Dagerbo Date: Mon, 01 Oct 2007 17:28:36 +0000 To: kdevelop-devel Subject: Re: Quickopen dialog Message-Id: <200710012123.26112.jens.dagerbo () swipnet ! se> X-MARC-Message: https://marc.info/?l=kdevelop-devel&m=119125971616178 On Monday 01 October 2007 19.09.44 Andreas Pakulat wrote: > On 01.10.07 21:46:50, kitts wrote: > > On Monday 01 Oct 2007 2:40:03 pm Andreas Pakulat wrote: > > > b) Translation Unit, does fit well? Wouldn't file fit better here and > > > be better known to the "general audience"? IMHO its a term too close to > > > the theoretic part of programming languages. > > > > You are right! As "general audience" i do not know what that "Translation > > Unit" means! ;-) Does it just mean any string int he code that is meant > > to be translated for localization? > > Just to educate you: Translation unit usually means a file in C++ and > also other languages. Its just an arbitrary amount of code that is to be > translated from the source language into the binary for (or interpreted > in the case of script languages). Its OTOH also used in the background > of translating texts (real-world as well as program-texts), at least > thats what wikipedia told me :) Unless I'm completely mistaken, a "translation unit" in C/C++ refers to all the "visible code" from one file context, that is it consists of the file being compiled _and all files included from that file_. I assume the "translation unit" setting in the suggested dialog would include information from all the header files as well, in which case I think the name is quite fitting. It isn't quite language-agnostic though. // jens _______________________________________________ KDevelop-devel mailing list KDevelop-devel@kdevelop.org https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel