|
But you did. You said "because RPG programs are not thread-safe"I am not saying they cannot.
Exactly. So you choose not to use it. Because it's too hard for you to learn or train or get adopted.I am just saying you are crazy to do it.
The same argument can be made for SQL. RPG wasn't "Built" to do SQL, SQL was added on later.RPG is not a language ever built to do multi-threading.
Your problem is really this. It is not just one RPG program you have to worry about. How many people have a clean stack? In other words, no legacy code anywhere in the stack?
Every single program in the stack has to be coded for multi-threading.
Introduce one program in the stack that is not thread-safe and you have a disaster
and every programmer who is working on a program on that stack has to know and understand multi-threading. That is not simple.
Even in languages that support it, multi-threading is a difficult problem. It is not just something you slap in.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.