User talk:Coppro~enwikibooks

Welcome message
Hello, and welcome to Wikibooks!

Here are some tips to help you get started:
 * To learn the wiki-markup-language syntax, see Help:Editing.
 * You should sign your name on Talk and vote pages using four tildes, like this: &#126;&#126;&#126;&#126;
 * There is a box at the top of the edit window that will insert this, too; it looks like part of a signature.
 * Remember to conduct any editing experiments in the sandbox.
 * You can tell the community something about yourself in your userpage.
 * You can get to this page by clicking the tab at the top of the page labeled with your registered username.
 * If you are a Wikipedian, see Wikibooks for Wikipedians for a primer on how things work here (it's a little different).
 * If you want to base your work here on materials from Wikipedia, please use WB:RFI (requests for importation) to bring the material over in compliance with the GFDL.
 * If you're an instructor and plan on using Wikibooks for a class project, see Guidelines for class projects
 * Please say hello at the Staff Lounge with any questions or ideas.
 * Eventually, you might want to read the Manual of Style and Policies and Guidelines.
 * Please take a look at Naming policy before starting a new book.
 * Remember to maintain a Neutral point of view.
 * Explore, be bold in editing pages, and have fun!

You will find more resources in Community Portal. If you want to ask a question, visit the Study help desk, the Staff lounge, IRC channel or ask me personally on my talk page. For site news, see the Bulletin board. It might be a good idea to add this page to your "watchlist" so that you can see when any new information is posted there. You can do that by clicking the tab labeled "watch" at the top of the page.

Good luck! --Panic 18:10, 12 September 2007 (UTC)

Hello again... C++ Programming
About the moving of the pointers and arrays from the operators section... What the logic behind moving them out of the section (since they are operators)?

I think I understand what irked you. Humm probably moving the C++ Programming/Operators/Pointers and C++ Programming/Operators/Arrays to a new location /Code/Types/ in the future...

Introducing Arrays and pointers without explaining operators first can be problematic in helping to understand the overloading of of operators and how to work with those derived types. Check C++ Programming/Code/Variables at the end and at this location in the book it would be better to make a note that those types exist (they are on the table) and point to the section were they are introduced giving freedom to the reader to select skipping or waiting until they are presented.

I also noted that you renamed the references given to the operators. I used the same that were referred on the table (I don't have any particular objection to your rename only about consistency, I will have to take a look on the standard to check how they are referred there, we should fallow as closely to the standard as possible...)

I made minor edits (some corrections were beyond wording), moved the page (and reference section from another page) to keep up with the navigation, corrected the headers levels as it broke the TOC and restored the removed array page.

(full C++ Programming/Chapter Fundamentals or specific section C++ Programming/Operators )

PS: You can reply here... --Panic 05:52, 19 September 2007 (UTC)

Well, what happened was that after I improved the existing section, I realized that it was more of a description of how to use pointers. For instance, why is there a section on NULL pointers in the operators section? I'm not really familiar with the way wikibooks actually works (and the policy documents are horrible to navigate), so I did the best I could. I'm thankful that you came along and fixed it up.

I don't take offense to any corrections you make, as you're much more familiar than I am with this. I think that the best way to do this is to start by moving the pointer and array descriptions into the variables page, and then having the operators cover the actual operations in-depth. The problem I have is with pointers being described in the operators section. In C++, IMHO, they're worthy of their own page. There are pointers to functions and pointers to members, and then the combination of the two. Maybe such an advanced page should follow classes, such that pointers-to-members can properly introduced. I'll continue to write about pointers to functions and member pointers at C++ Programming/Operators/Pointers/to functions and C++ Programming/Operators/Pointers/Member pointers respectively, since I can't do anything wrong there. Coppro 20:38, 20 September 2007 (UTC)

Yup that was what I thought about the move to a specific page... The problem with writing anything about C++ is that at some points dependencies are very difficult to maintain in a logical way as to facilitate the learning of the language, introducing pointers or arrays without the understanding of the operators that serve to declare and access this "derived" types is my believe, cause more confusion. I have attempted to structure the book as a mirror of how I would have liked I had learned the language, breaking the pages in smaller section and on specific points/subject will enable cross link and readers to skip/jump to other section in this I think our efforts coincide the problem is were we think the subject should rest for your edits I think you would like to insert it directly on the variable section. What I prosed above (and with my edits) is mention this specific types and point to the operators section (or even better to a specific pages of each type), for instance how would you propose explaining the operator & without first covering operators in general?

The same concept was what I proposed with C++ Programming/Operators/Pointers/to functions and C++ Programming/Operators/Pointers/Member pointers (names can be tweaked later, to functions and member functions would probably be better) the best place to "put" the text would probably be on the section dedicated to functions and classes, and reference those concepts on the pointers text (and on the functions also) pointing forward into the book. Do you agree or have a better solution that would keep some kind of logical structure to the covered subjects? --Panic 22:30, 20 September 2007 (UTC)

BTW if you can, please take a look into the reply I posted on Talk:C++ Programming/iostream maybe you can extend or correct some of the information I gave to that user... --Panic 22:34, 20 September 2007 (UTC)

I think that the best way to keep the structure would be to write about pointers in three places - 1) The variables page, where they can be introduced in a simple manner. 2) The operators page, where everything can be well-defined and worked on and 3) A new advanced pointers page where we could cover the uses of pointers and how they all interact. Other tidbits on pointers (like using the -> operator) could also be put in the appropriate page (the page on classes for ->, and the page on inheritance for dynamic_cast).

It's also worth noting that member pointers do not have to be member function pointers. The use of member non-function pointers is extremely rare, but imagine if you are writing an RPG, and every monster has 6 stats, and each one can range from 1-99. Now, let's say that these are private. You could have a bunch of functions for each one (e.g. getStr, performStrCheck, increaseStr). Instead, you could have a function returning a const int Monster::* for each stat, and then pass those around. In case it comes back to a function that requires modification (increaseStat, for instance), you can make an asssertion that it is a valid stat (which gets removed during the release build), and then remove the const-ness via a <tt>const_cast</tt> and modify. This shrinks the code, and makes more complex relationships possible between classes.

I unfortunately don't have that same dearth of knowledge as to the iostream answer. My best guess, though, would be that the <tt><<</tt> and <tt>>></tt> operators for primitives are actually performing the extraction or insertion. Most user-defined <tt><<</tt> and <tt>>></tt> operators (particularly <tt><<</tt>) are just transalting the streaming of one class into the streaming of all it's member variables. You can't do the same thing for an integer.

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Coppro. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Coppro~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:06, 17 March 2015 (UTC)

Renamed
<div class="plainlinks mw-content-ltr" lang="en" dir="ltr”> This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:49, 19 April 2015 (UTC)