Can we please, please stop breaking shit that worked just fine in '95?
Not the author's fault (apart from choosing to use Blogger), but wow, how do you fuck web design up that badly? It's just a blog, a few paragraphs and links to more articles, it doesn't need to be an entire fucking web app complete with 5 other useless ways to view a list of summaries (Pinterest is big right now, people love grids, right? Here, let me smack you in the face with this stupid zooming JQuery effect).
Now the pioneer of JS apps doesn't even bother trying to put <noscript>There is usually a blog post here if you are using javascript</noscript>
Because I feel your pain, I wrote you a quick, dirty fix.
# how to fetch a blogger.com blog
# without the gratuitous javascript
# usage: nameofthisfile blog.whatever.com > html_file
#! /bin/sh
case $# in
1)
{
a=${1%%/*}
printf "%b" "GET / HTTP/1.1\r\n";
printf "Host: ${a##http://}\r\n";
printf "Connection: Close\r\n";
printf "\r\n";
} \
|nc -vv $1 80 \
|sed '
/targetBlogID/!d;
s/.*targetBlogID=//;
s/&.*//;
' \
|while read a
do
{
printf "%b" "GET /feeds/$a/posts/default HTTP/1.1\r\n";
printf "Host: www.blogger.com\r\n";
printf "Connection: Close\r\n";
printf "\r\n";
} \
|nc -vv www.blogger.com 80 \
|sed '
s/</</g;
s/>/>/g;
s/&/\&/g;
s/"/\"/g;
1i\
<br><br>
s/<name>/<br><br>name &/g;
s/<uri>/<br>uri &/g;
s/<generator>/<br>generator &/g;
s/<id>/<br>id &/g;
s/<published>/<br>published &/g;
s/<email>/<br>email &/g;
s/<title type=.text.>/<br><br>&/g;
s/<openSearch:totalResults>/<br>total results &/g;
s/<openSearch:startIndex>/<br>start index &/g;
s/<openSearch:itemsPerPage>/<br>items per page &/g;
s/<updated>/<br>updated &/g;
s/<thr:total>/<br>thr:total &/g;
s/<\/feed>/&<br><br><br>/;
'
done
;;
*)
echo usage: $0 blog.whatever.com >&2
esac(to prevent confusion: this is a parody of the site MBlume linked)
http://unspecified.wordpress.com/2009/05/16/microsoft-bans-m...
http://msdn.microsoft.com/en-us/library/dswaw1wk(v=vs.80).as...
edit: I read the link you included and I have to take exception with this line:
it’s a perfectly safe function if you use
it properly
"If the source and destination overlap, the behavior of memcpy_s is undefined."
Wow, way to improve things microsuck! It's not like anyone has ever mistakenly used memcpy on overlapping buffers....
It's a little amusing that MS have this optional part of C11 implemented years in advance and standardised on their work, but haven't got C99 support. It must suit them to have it that way.
Can you tell me whether the C11 Bounds checking stuff from this optional Annex K had fully made it in to GCC 4.9? If not what's missing?
On the status page here it implies the project has had issues:[0]
[0]http://gcc.gnu.org/wiki/C11Status
Yet, on the release notes it says "Substantially complete" but it's really as clear as mud whether it's all there[2].
[2]http://gcc.gnu.org/gcc-4.9/changes.html
I suppose that on Linux and Windows the intel compiler relies on the GCC/MS implementation of memcpy_s.
#define const_cast CONST_CAST_IS_FORBIDDEN #define dynamic_cast DYNAMIC_CAST_IS_NEVER_NECESSARY
etc...
its dirty, but it gets the job done
These functions have no right to exist.
char dst[5];
sprintf(dst, "%.*s", (int)sizeof(dst)-1, "Hello!");
Just don't forget the "." or the "-1".
But banning gets is obvious because it is by definition facing external input
(It is perfect with no sidebar on Dolphin/Note 2. Arstechnica on the other hand has been broken for a few days already.)
My theory (based purely on using the site, mind you) is that the all the crazy dynamic display stuff in Blogger (before that, it was a much more normal/boring blogging platform) was one last hurrah before the project was relegated to "legacy barely-maintained-mode," and that it hasn't had proper testing in years...
Given that, I think really the best thing would be if they come up with a way to integrate it into Google+ and retire Blogger as a platform. Hopefully they'd add some more features[1] to G+ to keep the functionality roughly equivalent and support the longer-form type of article which is more common on blogs, and keep the domain and blog identities from Blogger around as a thin skin. At least then it would be well maintained.
[1] E.g. better markdown support, multiple embedded images, some sort of easier access to older articles (Blogger lets you browse by year/month), etc.
http://linux.die.net/man/1/gcc
-include file Process file as if "#include "file"" appeared as the first line of the primary source file. However, the first directory searched for file is the preprocessor's working directory instead of the directory containing the main source file. If not found there, it is searched for in the remainder of the "#include "..."" search chain as normal. If multiple -include options are given, the files are included in the order they appear on the command line.