From 1873814734821971285 X-Google-Thread: f78e5,f292bdd67daeb7bb X-Google-Attributes: gidf78e5,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!news.glorb.com!news.alt.net!comp-std-cpp-robomod!not-for-mail From: Seungbeom Kim Newsgroups: comp.std.c++ Subject: Re: C++ Embraces Procedural Programming Over OO Programming [OT] Date: Sun, 26 Nov 2006 23:28:18 CST Organization: Altopia Corp. - Usenet Access - www.altopia.com Lines: 36 Approved: Fergus Henderson , moderator of comp.std.c++ Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: news.Stanford.EDU 1164605001 6008 128.12.181.66 (27 Nov 2006 05:23:21 GMT) X-Complaints-To: news@news.stanford.edu Return-Path: X-Authentication-Warning: mulga.csse.unimelb.edu.au: fjh set sender to devnull@stump.algebra.com using -f X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-Original-To: std-c++@mailman.ucar.edu Delivered-To: std-c++@mailman.ucar.edu User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) X-Virus-Scanned: amavisd-new at ucar.edu X-Virus-Scanned: amavisd-new at csse.unimelb.edu.au X-Virus-Scanned: amavisd-new at csse.unimelb.edu.au Xref: g2news2.google.com comp.std.c++:4783 Sektor van Skijlen wrote: > This is exactly the greates problem with current standard. That there are no > standard "modules", so the standard is "everything or nothing". > > [...] > > The problem is that the standard must cope with two opposite situations: > - people need libraries for most required things (read: must have GUI) > - some platforms don't allow to implement some of those libraries (read: no > GUI possible) > > So, there are the following choices: > - select no GUI, leaving users that want to make GUI in C++ alone > - select GUI, making non-standard almost all compilers for emb. systems > - split the standard into modules and require the declaration for every C++ > implementation whether it supports particular modules > > Modules, of course, would have to be selected according to what is possible > for particular platform and it may contain language core features with library > parts as well. This may be GUI, exceptions, dynamic-allocated memory, etc. Not all implementations have standard input and output, but the C and C++ standards have required printf/scanf family and iostreams anyway. The same is for files. Does this mean those implementations haven't been conforming? Or is there any special provision made by the standards? -- Seungbeom Kim --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.comeaucomputing.com/csc/faq.html ]