From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,8143b93889fe9472 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.180.91.114 with SMTP id cd18mr46599wib.2.1359689890656; Thu, 31 Jan 2013 19:38:10 -0800 (PST) Path: bp2ni9431wib.1!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.108.MISMATCH!feeder2.cambriumusenet.nl!feed.tweaknews.nl!209.197.12.242.MISMATCH!nx01.iad01.newshosting.com!newshosting.com!216.196.98.142.MISMATCH!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newsfeed.news.ucla.edu!news.snarked.org!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Niklas Holsti Newsgroups: comp.lang.ada Subject: Re: Ada standard and maximum line lengths Date: Tue, 29 Jan 2013 14:31:25 +0200 Organization: Tidorum Ltd Message-ID: References: <8dfcf819-e1d0-4578-a795-a4bf724b5014@googlegroups.com> <5107b329$0$6556$9b4e6d93@newsspool4.arcor-online.net> Mime-Version: 1.0 X-Trace: individual.net Q0VvAQg+kZDqICqcF3hVgALmUAO2n6xul/tBqO9ZxqvxyfALZskpxF1FIEYxNJIkbQ Cancel-Lock: sha1:RSX0CbTjN6kEIjq0Qu2covXRcQ0= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 In-Reply-To: <5107b329$0$6556$9b4e6d93@newsspool4.arcor-online.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Date: 2013-01-29T14:31:25+02:00 List-Id: On 13-01-29 13:31 , Georg Bauhaus wrote: > On 29.01.13 11:25, Niklas Holsti wrote: >> 200 characters is ok as a max line >> length. 200 for an identifier is overkill, IMO. > > When the meaning of "meaning" is defined by a programming > environment, naming capabilities may need to tackle names that the > environment imposes on the source. The names may exist for, and be > shaped by, hysterical raisins. For example, the following is listed > as a symbol from the text section of a standard C++ library: > > __ZNSt3__112basic_stringIwNS_11char_traitsIwEENS_9allocatorIwEEE6insertIPKwEENS_9enable_ifIXsrNS_21__is_forward_iteratorIT_EE5valueENS_11__wrap_iterIPwEEE4typeENSD_IS8_EESB_SB_ As you well know, that is a compiler-generated mangled "symbol", not a user-written identifier. Its extreme length is an artefact of the historical limitations on linkers and the linking process, in particular the lack of name-space control and of overloaded symbols (resolved by type or profile) and the requirement for separate compilation of modules without any central compilation/information library. This forces the C++ compiler to encode many properties of the C++ object, named by some much shorter source-code identifier, into the symbol used for linking. Even for hypothetical SW of some sort that generates Ada source code automatically, I think it very unlikely that it would generate identifiers of that length, since Ada identifiers can be qualified and sorted into packages etc. much more flexibly than is the case for linker symbols. -- Niklas Holsti Tidorum Ltd niklas holsti tidorum fi . @ .