Re: [Algorithms] C++ inherited constructors
Brought to you by:
vexxed72
From: Scott M. <sc...@3d...> - 2000-07-17 14:13:10
|
This question would probably be more welcome on the Software Engineering Gamedev list (sweng-gamedev). Here's the info for it in case you're interested. ------------------------------------------------ Welcome to the sweng-gamedev mailing list! Please save this message for future reference. Thank you. If you ever want to remove yourself from this mailing list, you can send mail to <Maj...@in...> with the following command in the body of your email message: unsubscribe sweng-gamedev or from another account, besides sc...@3d...: unsubscribe sweng-gamedev sc...@3d... If you ever need to get in contact with the owner of the list, (if you have trouble unsubscribing, or have questions about the list itself) send email to <own...@in...> . This is the general rule for most mailing lists when you need to contact a human. Here's the general information for the list you've subscribed to, in case you don't already have it: The Game Software Engineering List Charter ========================================== Welcome to SwEng-Gamedev! This list is provided as a forum for game developers to discuss and develop software engineering strategies for developing their engines. Discussion of game patterns and other abstractions is heartily encouraged! Case studies (unless in violation of an NDA!) are also a welcome way to learn -- a game-engine autopsy of sorts. Discussions of lower-level programming issues like individual algorithms and their implementation is generally discouraged. However, there are exceptions; if an algorithm is of a broad enough scope that it deserves abstractions in its implementation, for instance, it's worth discussing. And nobody likes a list plagued by people shouting "OFF-TOPIC! GET OUT!" so let's generally try to allow for a little wiggle room in discussions. Furthermore, as C/C++ are the primary languages used today for game development, discussions of patterns will likely use reference implementations or example headers in one of these languages. Other languages are certainly welcome, but before writing up an example in Prolog, consider how useful it'll be to most of the list. Furthermore, this isn't an appropriate place to evangelize your favorite obscure language. Also, as alluded to above, it's important that discussions take intellectual property laws and professionalism into account. For every subscriber, the following rules apply: 1) Your company must know you are on this list. 2) Assume all things you say on this list will be public. 3) No open recruiting. Hopefully, by sticking to these, we'll keep discussing both smoothly flowing and also legal! To send mail to the list, send to 'swe...@in...'. Enjoy! |