Hello
Hello, world!
I like beautiful things. I like creating beautiful and simple things. I like recursion in nature.
I hope to write here beautiful ideas.
I think most software today is complicated and ugly. I think mainstream programs, especially operating systems are 40 year old designs driven to absurd scale by corporations or user inertia. I believe there's very little inovation going on that influences the industry in some positive way.
I think software should be beautiful and understandable. My opinion is that most software we run today is not. For me, Plan9 is a beautiful operating system, and C and Go are beautiful programming languages.
The title of this blog is a reference to its thematics. I'm proposing a puzzle to my readers. Find out what the title means, what it does, and what beautiful idea does it implement? I'm going to leave you a hint in this post's label.
Oh, and I work as a software engineer but I don't think that's important.
Bit Banger posted on August 3, 2011 9:44 PM
http://lmgtfy.com/?q=%22JSR+PC%2C+%40(R6)%2B%22&l=1
next time pick a co-routine call instruction that's not in the google-indexed pdp manual :P
Aram Hăvărneanu posted on August 4, 2011 1:00 AM
The point of this puzzle is to expand your horizon, not to be obscure or arcane. It's obviously PDP-11 assembly. Yes, you can look it in the manual. In fact, you are expected to look it up in the manual :-).
The real question is what service it can provide and how does it provide this service. The answer to this question is mind-expanding to most people.
You haven't answered anything. What exactly is this used for and how does it work? :-).
undergraver posted on August 4, 2011 2:56 PM
Nice. http://en.wikipedia.org/wiki/Coroutine#Implementations_in_assembly_languages you can see your instruction in another (equivalent) form ("JSR PC,@(SP)+") there.
When referring to coding I think that the difference between cooperative scheduling and preemptive scheduling is that while the former offers deterministic execution times and reliability the latter offers "simplicity" in programming.
By "simplicity" I mean that people are most of the time unaware of the traps of not-well-synchronized concurrent code. Sure, the code is easier to write/test and to control(most of the time), that's why it is so wide spread.
bitbanger posted on August 4, 2011 5:21 PM
You haven't answered anything.
i beg to differ: next time pick a co-routine call instruction...
for someone familiar with the concept it requires no further explanation as it's been around forever and is well understood & documented. i guess my presumptions are off :P
Post a Comment