It is time once again to check Programmers, this time it is using some real Machine Learning to classify this message, I wonder what the classification score will be? — Simon Forsberg 26 secs ago

It is time once again to check programmers, this time it is using some real Machine Learning to classify this message, I wonder what the classification score will be? — Simon Forsberg 16 secs ago

@Olaf, of course. You are right call out the fact that the S field code is not in standard ISO C. I am simply attempting to clarify for the same inexperienced programmers you mention that that is the sense in which it is "non-standard". And also, perhaps, to point out that not every C feature in the POSIX standard (or in any vendor's documentation) is a feature of ISO C. — John Bollinger 33 secs ago

This question is off-topic here. This site is for programming and programmers tools related questions, not general computer or software support. You're looking for Super User instead. Voting to migrate it there. — Ken White 21 secs ago

The correct thing should be to drop the piano on the compiler writers who, given T *p;, are unwilling to regard *(U*)p=whatever; as being a potential access to things of type T or U, but would instead insist that programmers use memcpy, which compilers must treat as a potential access to things of every type even when the programmer knows the pointer will never identify anything that isn't a T or U. I don't know why compiler writers decided they could make the world a better place if they force programmers to write code which is harder to read and less optimizable, but they did. — supercat 19 secs ago

Yes, that's the answer. If it is just C and C++ then it is difficult to understand why it is done that way. To understand we must put things in the context of the old way of statically linking. Static linking seems primitive to Windows programmers but it is the primary reason C cannot mangle names. — user34660 21 secs ago

There's also a really good article that demonstrates this exact issue. kalzumeus.com/2010/06/17/… — Chris 33 secs ago

You might want to head over to programmers.stackexchange.com — azurefrog 1 min ago

@azurefrog: are you sure that this is on-topic at programmers? — Hovercraft Full Of Eels 40 secs ago

You might have better luck by asking on the /r/haskell subreddit. There's a good mix of Agda programmers and Freer enthusiasts on there. — haoformayor 14 secs ago

Alright... I kind of like this answer - but it doesn't exactly answer the question to the standards of a site for programmers :/ — Zizouz212 53 secs ago

General rule is.. Content Retrieval = GET. Content Update = POST. Get requests are idempotent. They can be safely run multiple times without actually the system. Post requests usually are not idempotent. While you can use these methods in ways they're not intended to be used, it typically causes poor usability (inability to bookmark search results, or detail screens etc.) and causes confusion for other programmers maintaining your work. — user1751825 31 secs ago

@icecub General rule.. Retrieval = GET. Update = POST. Get requests are idempotent. They can be safely run multiple times without altering the data in the system. Post requests usually aren't idempotent, as they POST content to the system. Adding a new type of food to the database, for example. Running it multiple times results in duplicated content. While you can use these methods in ways they're not intended to be used, it typically causes poor usability (inability to bookmark search results, or detail screens etc.) and causes confusion for other programmers maintaining your work. — user1751825 35 secs ago

@user1751825 I sincerely do not think you know what you are talking about, on several levels. POST is fine for what the OP has stated they wish to do. Both post and get send data to the server, and these days most competent programmers use post almost exclusively, and we always build-in tests to prevent duplicated content - even when using GET requests. — gibberish 26 secs ago

This site is for programming (code) and programmers tools related questions, not hardware recommendations. In addition, questions asking for recommendations are listed as being off-topic in the help center guidelines - see the list of numbered items on that page, and specifically item #4 in that list. Good luck. — Ken White 32 secs ago