It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I am looking for a good material on different thread synchronization primitives that are generic (not tied to any language or implementation. I only want the concepts).
Searches in the internet point to specific language or implementation.
Well, it will be hard to find such resources, because they are almost always accompanied with some (at least pseudo) code example. Unless someone better informed than me sees this question :)
I would suggest exploring wikipedia for starters, e.g.:
Producer consumer problem
Dining philosophers problem
Sleeping barber problem
Synchronization (computer science)
Inter-process communication
look at the linked general words, links and external links, once you get familiar enough in the desired direction it would be ideal to find a scientific article that covers the topic - they are full of many references, and evenutally you'll stumble upon some great article(s).
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I know that I need to know at least C and Assembly. In your own opinion what else does one need to know apart from knowing how to program in C and Assembly efficiently? Are there any books you can suggest to get me started? I also read that you need to know about the hardware architecture of the platform you are emulating. Would you also recommend the books listed here?
For experts only
You would have to know all the inner workings and hardware details of PSP, which are business secrets of Sony and therefore not published. The way most emulators are made is reverse engineering, a process in which the device itself is disassembled and its inner workings are studied. That includes analyzing the chips thoroughly, reading the contents of ROM chips and sometimes even deciphering encrypted data. Full analysis usually requires specialized equipment and years of engineering experience.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
Can anyone tell me links for reading about mainframe internals like what happens in mainframe intrenally when I login or create a dataset or submit a job. I googled but couldnt find
Thanks in advance
The Principles of Operation will give you as low-level a look at mainframe internals as you're likely to get.
You mention wanting to know what happens internally "when I login or create a dataset or submit a job." You might want to ask yourself, "login to what?" exactly. TSO? CICS? IMS?
For creating datasets you might start with DFSMS.
For submitting jobs you might want to start with JES2 or JES3, depending on which one you're using.
None of what you're asking is a small topic.
A mainframe is fundamentally just like any other computer - it is just a matter of scale that differentiates a mainframe from a desktop. Fundamentally, what happens when you log in to a Windows desktop is very similar to what happens when you log in to a mainframe. The details are very different but fundamentally you are doing the same thing.
The links cschneid provided in his answer will give you a lot of the finer detail, but conceptually, what goes on inside a mainframe is similar to what goes on in any computer these days.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 12 years ago.
Assuming you have basic to intermediate knowledge of a particular language, how can you become an expert in that language in a short amount of time?
Refer to this 21 Days by Peter Norvig
Pull all your information sources together - such as:
The official language documentation,
Best practice books,
Google around for tutorial sites,
Get used to searching and finding what you need quickly
The obvious reply would be: Practice makes perfect.
Try to work with the language on daily basis and push yourself out of your comfort zone in using it. Joining a user group is also a good option.
But at the end of the day, I must agree with Rozuur and concede that becoming an expert in something usually requires experience and experience requires time.
I think,
Passion: to explore and learn, and then
Dedication: to learn different aspects of that programming language, finally,
Patience: to design a project and apply all that one has learned into it.
Note:The programming languages these days have grown too big to implement above strategy.
However, I would still believe that passion is the key to all learning!
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 12 years ago.
What practice or practices are good 90% of the time when working with threading with multiple cores?
Personally all i have done was share immutable classes and pass (copy) data to a queue to the destine thread.
This is very vague - but there are a few basic precepts I'd always follow:
Make sure threading makes sense before you implement it
Focus on algorithms, not individual lines of code when designing for threading
Thread at the highest level possible
Prefer immutable data
Synchronize data access appropriately
Prefer high level threading libraries over low level, hand written threading code
Measure (make sure 1. was true!)
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 12 years ago.
In this programming world of ours we see C sharp and Java on the top. But these have rich library of thousand classes and function which become more richer with their new editions. Can we have a programming language which can give us more creativity and innovation inspite of this ever increasing library based languages ?
There are plenty of such languages: Ruby, Python, JavaScript, Erlang and plenty of others. You just need to stop trolling and do your homework.
Assembly. Can't get much more free then that.
In fact any decent library or framework is a language itself. A domain specific language. Of course you could have all the same functionality in form of a variety of "proper" DSLs, but it won't be that much different from the current state.