<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>comp.std.c Google Group</title>
  <link>http://groups.google.com/group/comp.std.c</link>
  <description>Discussion about C language standards.</description>
  <language>en</language>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/b99a7c897c7a5f80?show_docid=b99a7c897c7a5f80</link>
  <description>
  Well, this is funny. Imagine, overloading in assembler! &lt;br&gt; Who is going to dispatch? The assembler? That would be &lt;br&gt; *really* a smart assembler! &lt;br&gt; Obviously if you are not writing in C, you must use the fixed &lt;br&gt; interface and you can&#39;t use overloading. This is the same situation &lt;br&gt; as you have today. The advantage to C++ overloading is that
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/b99a7c897c7a5f80?show_docid=b99a7c897c7a5f80</guid>
  <author>
  ja...@nospam.com
  (jacob navia)
  </author>
  <pubDate>Mon, 08 Sep 2008 06:47:43 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/a007950e8bfb40c9?show_docid=a007950e8bfb40c9</link>
  <description>
  If you&#39;re trying to use the interface from assembler, libffi, C# P/Invoke, &lt;br&gt; or other similar methods, you can&#39;t use the overloaded interface, but must &lt;br&gt; instead use the type-specific routines. &lt;br&gt; The problem with opaque overloading is that you&#39;re precluded or hindered &lt;br&gt; from knowing the name and/or location of the procedure altogether, unless
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/a007950e8bfb40c9?show_docid=a007950e8bfb40c9</guid>
  <author>
  will...@wilbur.25thandclement.com
  (William Ahern)
  </author>
  <pubDate>Mon, 08 Sep 2008 05:36:00 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/03e1515297edf306?show_docid=03e1515297edf306</link>
  <description>
  Yes you need to make sure that you avoid using them, but no you don&#39;t have &lt;br&gt; to know what exactly they are. They&#39;re just internal symbols used by the &lt;br&gt; library. Even without overloading, most non-trivial libraries do need to &lt;br&gt; reserve a chunk of the namespace for their internal symbols, and they &lt;br&gt; typically do that by documenting a single prefix rather than by listing all
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/03e1515297edf306?show_docid=03e1515297edf306</guid>
  <author>
  wojte...@yahoo.ca
  (Wojtek Lerch)
  </author>
  <pubDate>Mon, 08 Sep 2008 01:08:39 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/a675517ce1835383?show_docid=a675517ce1835383</link>
  <description>
  It doesn&#39;t really matter if the mangling is done by the developer or &lt;br&gt; the compiler. Either way, the fundamental problem with name mangling &lt;br&gt; is pollution of the name space. If I&#39;m using a third party library &lt;br&gt; that overloads my_sqrt(), don&#39;t I have to know what their mangled &lt;br&gt; names are (sqrti, sqrtC), and make sure that I avoid using them? In
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/a675517ce1835383?show_docid=a675517ce1835383</guid>
  <author>
  jameskuy...@verizon.net
  </author>
  <pubDate>Mon, 08 Sep 2008 00:16:02 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/cf75eb57518aa85c?show_docid=cf75eb57518aa85c</link>
  <description>
  Exactly &lt;br&gt; It will replace the my_sqrt function according to the actual &lt;br&gt; arguments given. If double it will call sqrt, &lt;br&gt; etc. &lt;br&gt; Maybe there are problems related to this method? &lt;br&gt; I do not think so.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/cf75eb57518aa85c?show_docid=cf75eb57518aa85c</guid>
  <author>
  ja...@nospam.com
  (jacob navia)
  </author>
  <pubDate>Sun, 07 Sep 2008 20:17:26 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/05d71e5b4b81d8fa?show_docid=05d71e5b4b81d8fa</link>
  <description>
  &amp;quot;jacob navia&amp;quot; &amp;lt;ja...@nospam.com&amp;gt; schreef in bericht &lt;br&gt; So suppose I&#39;m using a library using this overloaded function the compiler &lt;br&gt; can detect it and replace my_sqrt with the appropriate function? Maybe there &lt;br&gt; are problems related to this method?
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/05d71e5b4b81d8fa?show_docid=05d71e5b4b81d8fa</guid>
  <author>
  z...@woaini.com
  (Lassie)
  </author>
  <pubDate>Sun, 07 Sep 2008 19:29:26 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/df9d621cc6fe45cd?show_docid=df9d621cc6fe45cd</link>
  <description>
  Yet it missed the opportunity to expose intrinsics like GCC&#39;s &lt;br&gt; __builtin_choose_expr and __builtin_types_compatible_p, necessary for &lt;br&gt; implementing tgmath.h. Any name mangling would be done by the code authors, &lt;br&gt; not the compiler, leaving the status quo intact. &lt;br&gt; Alternatively, it could have standardized on GCC&#39;s compound expressions and
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/df9d621cc6fe45cd?show_docid=df9d621cc6fe45cd</guid>
  <author>
  will...@wilbur.25thandclement.com
  (William Ahern)
  </author>
  <pubDate>Sun, 07 Sep 2008 18:00:43 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/a947ac72063a71e6?show_docid=a947ac72063a71e6</link>
  <description>
  he C compiler lcc-win implements function overloading as an extension. &lt;br&gt; The often heared argument &amp;quot;It would require name mangling&amp;quot; can be &lt;br&gt; &amp;quot;casted away&amp;quot; with &lt;br&gt; double sqrt(double); &lt;br&gt; double sqrti(int); &lt;br&gt; double sqrtC(long double); &lt;br&gt; int overloaded my_sqrt(double) = sqrt; &lt;br&gt; int overloaded my_sqrt(int) = sqrti(int);
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/a947ac72063a71e6?show_docid=a947ac72063a71e6</guid>
  <author>
  ja...@nospam.com
  (jacob navia)
  </author>
  <pubDate>Sun, 07 Sep 2008 17:45:31 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/1612cb98491a3ede?show_docid=1612cb98491a3ede</link>
  <description>
  The C compiler lcc-win implements function overloading as an extension. &lt;br&gt; The often heared argument &amp;quot;It would require name mangling&amp;quot; can be &lt;br&gt; &amp;quot;casted away&amp;quot; with &lt;br&gt; double sqrt(double); &lt;br&gt; double sqrti(int); &lt;br&gt; double sqrtC(long double); &lt;br&gt; int overloaded my_sqrt(double) = sqrt; &lt;br&gt; int overloaded my_sqrt(int) = sqrti(int);
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/1612cb98491a3ede?show_docid=1612cb98491a3ede</guid>
  <author>
  ja...@nospam.com
  (jacob navia)
  </author>
  <pubDate>Sun, 07 Sep 2008 17:45:00 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/bf2044b782898fd6?show_docid=bf2044b782898fd6</link>
  <description>
  C99 does have limited function overloading; see the &amp;lt;tgmath.h&amp;gt; header. &lt;br&gt; But it doesn&#39;t allow programmers to define their own overloaded &lt;br&gt; functions.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/bf2044b782898fd6?show_docid=bf2044b782898fd6</guid>
  <author>
  ks...@mib.org
  (Keith Thompson)
  </author>
  <pubDate>Sun, 07 Sep 2008 17:41:28 UT
</pubDate>
  </item>
  <item>
  <title>Re: function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/179d1f0d90f020be?show_docid=179d1f0d90f020be</link>
  <description>
  Implementation complexity. It would require name-mangling, the &lt;br&gt; lack of which is an enormous boon to interfacing C with other &lt;br&gt; low-level languages (especially assemblers).
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/179d1f0d90f020be?show_docid=179d1f0d90f020be</guid>
  <author>
  apoels...@supernova.home
  (Andrew Poelstra)
  </author>
  <pubDate>Sun, 07 Sep 2008 16:13:14 UT
</pubDate>
  </item>
  <item>
  <title>function overloading</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/cd0fee2b283281fe?show_docid=cd0fee2b283281fe</link>
  <description>
  Just curious, why is function overloading not in C? C99 added loads of &lt;br&gt; functions to deal with the different real types (sqrtf, sqrtl etc)but this &lt;br&gt; couldve been solved more elegantly with function overloading. &lt;br&gt; Whats the disadvantage of function overloading that I&#39;m overlooking?
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/da43628c0bbb4461/cd0fee2b283281fe?show_docid=cd0fee2b283281fe</guid>
  <author>
  z...@woaini.com
  (Lassie)
  </author>
  <pubDate>Sun, 07 Sep 2008 12:33:57 UT
</pubDate>
  </item>
  <item>
  <title>Re: Trigraphs forever</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/dbe5f525c9e937ae/d22018d2a2fdc02c?show_docid=d22018d2a2fdc02c</link>
  <description>
  Yes, and it isn&#39;t just compilers which process such strings. &lt;br&gt; There are many trigraph-oblivious tools such as &amp;quot;yacc&amp;quot;, &amp;quot;indent&amp;quot;, &lt;br&gt; and of course locally-written tools such as one that gave heartburn &lt;br&gt; to my employer about 10 years ago: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://groups.google.com/group/comp.std.c/msg/c1d359a187566ed7?hl=en&amp;dmode=source&quot;&gt;[link]&lt;/a&gt;
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/dbe5f525c9e937ae/d22018d2a2fdc02c?show_docid=d22018d2a2fdc02c</guid>
  <author>
  t...@login020.unx.sas.com
  (Tom Truscott)
  </author>
  <pubDate>Fri, 05 Sep 2008 16:13:28 UT
</pubDate>
  </item>
  <item>
  <title>Re: Please Explain Me About This Behaviour..,</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/80a60dabd6523f9e/c2ca0483058cc8cc?show_docid=c2ca0483058cc8cc</link>
  <description>
  NOTHING .., SORRY.., I JUST THOUGHT THE MEMBERS ARE DIFFERENT.., I &lt;br&gt; WILL TAKE CARE NEXT TIME..,
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/80a60dabd6523f9e/c2ca0483058cc8cc?show_docid=c2ca0483058cc8cc</guid>
  <author>
  pranav...@gmail.com
  (Pranav)
  </author>
  <pubDate>Sat, 06 Sep 2008 03:14:21 UT
</pubDate>
  </item>
  <item>
  <title>Re: Thoughts about the new standard</title>
  <link>http://groups.google.com/group/comp.std.c/browse_thread/thread/bcfe43b0caef6cd0/6460f2ecc32e7485?show_docid=6460f2ecc32e7485</link>
  <description>
  Originally, C allowed pretty much anything as the left operand, so the &lt;br&gt; distinction was quite necessary.
  </description>
  <guid isPermaLink="true">http://groups.google.com/group/comp.std.c/browse_thread/thread/bcfe43b0caef6cd0/6460f2ecc32e7485?show_docid=6460f2ecc32e7485</guid>
  <author>
  lawrence.jo...@siemens.com
  </author>
  <pubDate>Fri, 05 Sep 2008 21:00:51 UT
</pubDate>
  </item>
  </channel>
</rss>
