Apologies about the overlinking in this edit -- I accidentally reverted to one version too early, undoing your (good) edit from July that removed the unnecessary links. Sorry about that, and thanks for putting everything in order. --JBL (talk) 14:36, 12 October 2018 (UTC)[reply]
Thanks for deleting it. It was a minor clean-up, but a good one.
Though I've been editing Wikipedia for nearly a dozen years now, this was the first time I'd ever added an image to an article, and I guess I was so focused on getting that part right that I failed to notice the white space I'd created.—PaulTanenbaum (talk) 13:32, 6 November 2018 (UTC)[reply]
The way the wiki software transforms the markup into web pages is somewhat, um, baroque, and the way it handles whitespace is really confusing (e.g. in bulleted lists, where double-spacing the entries breaks the list into multiple lists, see MOS:BULLETLIST).
Hey, about the "angry fruit salad"... part... I suppose that means my image is too messy?
Sorry about that. I was worried that might be the case.
I noticed you removed the part about "See Programming languages." I guess that wasn't neccessary but for now what should I do to provide a non-overwhelming example of the article's subject?
I want to highlight what is responsible for what so people who don't understand any .NET languages can get an idea, since I haven't seen much of a deep review of those things when looking at the example under Programming languages.(if you know what i mean. Or not. I dont know)
I removed that "See Programming Languages" mostly because it's a submarine link in the sense of MOS:SUBMARINE: it's a piped link where the link target is not obvious from the link text. (As a reader I would have believed this link to lead to Programming language.)
Re: "angry fruit salad", see wiktionary:angry fruit salad. I think the image you added is quite unclear, and the descriptions used in the image are a bit hard to read, at least with the image size used in the article.
The article Entry point is not specific to .NET, and I think too much emphasis on .NET languages in the lead section of that article may actually be misleading to the reader.
Another point I am not happy with is the sentence "A common form of the main function in C, C# or C++, is a static method, either returning no data (void) or a number (int), also known as the return code." Three points:
In C there are no methods or member functions, just plain functions.
In C++ the main function cannot be a static member function.
The return type of the main function in C and C++ must be int, it cannot be void. (Strictly speaking in C++ the main function is not really a function, e.g. it must not be called from the program itself and its address must not be taken. See the explanation of the main function at cppreference.com and at, well, Entry point#C and C++.)
You are right. I read about greatest and least elements and posets. I was thinking that "equals" is sort of binary relation like "two elements with the same value" or something. Actually here "equals" means "the same element". And in posets there are incomparable elements instead, that is not a ≤ b and not b ≤ a. And difference between greatest and maximal elements is that all elements are ≤ greatest element, but ≤ or incomparable with maximal element(s). 176.59.144.14 (talk) 12:39, 24 December 2018 (UTC)[reply]
You've been identified either as a previous member of the project, an active editor on Apple related pages, a bearer of Apple related userboxes, or just a hoopy frood.
WikiProject Apple Inc. has unexpectedly quit, because an error type "unknown" occured. Editors must restart it! If you are interested, read the project page and sign up as a member. There's something for everyone to do, such as welcoming, sourcing, writing, copy editing, gnoming, proofreading, or feedback — but no pressure. Do what you do, but let's coordinate and stay in touch.
See the full welcome message on the talk page, or join the new IRC channel on irc.freenode.net named #wikipedia-en-appleincconnect. Please join, speak, and idle, and someone will read and reply.
Yes, I think so. The more because mathematical operands are hardly identifiable as 'object' and 'subject' – when calculating 5 – 2 we usually say "subtract 2 from 5", but we can say "decrease 5 by 2" as well. For "add 3 to 7" I honestly can't say whether it should be 3 + 7 or 7 + 3. Hence I'd support removing those links. --CiaPan (talk) 13:16, 10 December 2019 (UTC)[reply]
dear sir i added a usewful external link a fractran interpreter in c very near to machine level. i did not understand why it is removed/ wolfram a commercial companys link is kept why not a useful interpteter .u can mail me at anilped@hotmail.com .
i want to understand i am not a good at word processors but professor of mathematics and computer science.
wish u healthy life thanks
@Anilped:, first of all, sorry for the late reply.
Awesome, I want to let you know that I appreciate it a lot, whatever you may say. We are making the best encyclopedia of all time, together. Our diverse opinions make up a significant part of human culture. --Ysangkok (talk) 16:21, 30 June 2020 (UTC)[reply]
There are no Beethoven entries in Symphony (disambiguation), just as there should be no Mozart entries in Kyrie (disambiguation). Here's a test for determining whether an entry is a partial match or not. If you refer to "Mozart's Kyrie", is it unambiguous? No, because you have to further disambiguate it. That's why I deleted what I did and kept the sole Vivaldi work. (I'm not a big classical expert, so if he composed more than one, then that should go too.) Clarityfiend (talk)
@Clarityfiend:: I see, thank you for that explanation. You are right, "Kyrie" could be viewed as similar to "Symphony" as they both can refer to works in musical genres also referred to as "Kyrie" and "Symphony", and it wouldn't make sense to list every work called symphony at Symphony (disambiguation). However, as a reader I use disambiguation pages as tools to navigate Wikipedia, and I think it is confusing to find the Wikipedia article on Vivaldi's setting of the Kyrie listed at Kyrie (disambiguation) and not the Wikipedia articles of other composers' Kyries. Unfortunately, Kyrie#Musical settings is not much help here.
Per MOS:DAB, "Do not add a link that merely contains part of the page title". The Vivaldi entry bothered me too. Upon further perusal, I only see it referenced as "Kyrie, RV 587" or "Kyrie in G Minor, RV 587", so I agree: all three should be transferred to Kyrie someplace, maybe in a new "Examples" or "Notable kyries" subsection under "Musical settings". Clarityfiend (talk) 05:14, 31 August 2020 (UTC)[reply]
I see you reverted an edit I made to UTF-8. I noticed that the table as I changed it had a minor error, that for technical reasons the first byte of a UTF-8 sequence cannot be $C0 nor $C1. (Actually, according to the rules those bytes should not appear in a UTF-8 character sequence at all.) I have corrected the table format and included a footnote explaining this. Thank you for your attention, I might not have noticed the error otherwise. Paul Robinson (Rfc1394) (talk) 17:30, 7 November 2020 (UTC)[reply]
virtual function call on construct c++ fatal runtime
OK, I will try my hand at it. Please nag me in a few days if I haven't added this to virtual function by then. And for what it's worth, this issue has been addressed in the sense that the C++ standards have always described the effect of making a call to a pure virtual function directly or indirectly from a constructor or destructor for the object being created or destroyed as undefined, in the sense of undefined behaviour. It's one of the many, many ways to shoot yourself in the foot with C++. – Tea2min (talk) 14:18, 3 December 2020 (UTC)[reply]
Thank you for a msg.
My point was that writing a very simple 20 lines of code compiler nor linker issues any warning (default warning setup), and leaves a program to crash at runtime.
I would assume if optimizer can unroll loops could traverse through three class relationship, especially no pointers used.
cl/linker used: Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29334 for x64, Microsoft (R) Incremental Linker Version 14.28.29334.0 — Preceding unsigned comment added by 24.45.193.41 (talk) 17:14, 3 December 2020 (UTC)[reply]
C++ is riddled with undefined behaviour. One of the implications of the use of the term "undefined" in the C++ standards is that a conforming implementation is not required to detect undefined behaviour. The kind of static program analysis/devirtualization required to detect the pure virtual function call your code example showed at compile time is expensive in terms of compilation time, and I would not expect C++ compiler writers to spend much energy on this problem. C++ compiler writers generally are expected to spend more energy on code optimization than on error detection. That's just the way it is, I'm afraid.
As I tried to explain in my edit comment when I removed the section you added to the article Virtual function, I did that mostly because I found it hard to read and unclear, and too specific for Microsoft Visual C++. I won't revert if you decide to add it back to the article as it was. However, it would need to be revised significantly, in my humble opinion. – Tea2min (talk) 17:56, 3 December 2020 (UTC)[reply]
Thank you for reply. Well I got to think what todo with this, years I thought performance-wise not many languages come close to c/c++.
I realize since old days language still has compile-as-written philosophy, its not a sandbox, but dang this object inheritance since concept is nothing than linking few code pages/classes together, there no loops, no runtime construction or pointers, all is written static just to be run.
Virtual function issue should have been solved, not for developer to think about. I tried to refactor some old code, instead of calling virtual I put extra middle layer class and call a wrapper instead, it compiled all nice, just to see it collapse on a launch.
Thought this language drives the coding, very deterministic in comparison to others, compiler does low level/optimization/symbolic reduction etc, but I don't know what they spend time on syntax rule lists and junk, could fix this first. — Preceding unsigned comment added by 24.45.193.41 (talk) 09:37, 4 December 2020 (UTC)[reply]
You may want to consider using the Article Wizard to help you create articles.
Hello, and welcome to Wikipedia. This is a notice to inform you that a tag has been placed on Hanan requesting that it be speedily deleted from Wikipedia. This has been done under section A1 of the criteria for speedy deletion, because it is a very short article providing little or no context to the reader. Please see Wikipedia:Stub for our minimum information standards for short articles. Also please note that articles must be on notable subjects and should provide references to reliable sources that verify their content.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. Egeymi (talk) 12:36, 23 December 2022 (UTC)[reply]
Hello Tea2min. Why did you undo the correction of ~ to ≈? The meaning of ~ is “is proportional to” while ≈ means „approximately“? That are two different meanings. Which symbol shall be used when “is proportional to” is meant? C.wolke (talk) 13:00, 16 November 2024 (UTC)[reply]
As I had tried to explain in my edit comment, I reverted your change because it changed "straight" to "curly" quotation marks, see MOS:CURLY. I agree that ≈ is certainly more correct than ~. I should have have kept that part of your change. I apologize. Tea2min (talk) 21:15, 16 November 2024 (UTC)[reply]
An editor has identified a potential problem with the redirect Two-way communiation and has thus listed it for discussion. This discussion will occur at Wikipedia:Redirects for discussion/Log/2022 October 27#Two-way communiation until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. Shhhnotsoloud (talk) 18:32, 27 October 2022 (UTC)
