| delorie.com/archives/browse.cgi | search |
| From: | "sl" <junk AT bbs DOT darktech DOT org> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: inline functions -- unknown references |
| Date: | Sun, 02 Jan 2000 01:00:47 -0500 (EST) |
| Organization: | Posted via Supernews, http://www.supernews.com |
| Lines: | 23 |
| Message-ID: | <fyoofqnexgrpubet.fnp21b0.pminews@nntp.generation.net> |
| References: | <200001010422 DOT WAA03622 AT lakdiva DOT slt DOT lk> |
| X-Complaints-To: | newsabuse AT supernews DOT com |
| X-Newsreader: | PMINews 2.00.1205 For OS/2 |
| MIME-Version: | 1.0 |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
| Reply-To: | djgpp AT delorie DOT com |
On Fri, 31 Dec 1999 22:23:18 +0600, Kalum Somaratna aka Grendel wrote: >I think what you should do is that you should move your say >plotpixel and other inlined fuctions to header files. The problem is that in C++, this gets VERY ugly when you stick the implementation of a member function in the middle of a class. I insist of leaving all implementation in the .cc file.. >I hope this helps and is clear. Please donot include the source as >#include name.cc instead copy the inline fuctions to a header file >and include it. I tried doing #include "name.cc", and that failed.. Shouldn't this work in theory? >Best Wishes to everyone for the new milennium. Yup, happy new year! :) Gili
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |