Friday, December 2, 2016

Digest for comp.programming.threads@googlegroups.com - 25 updates in 11 topics

Ramine <ramine@1.1>: Dec 02 06:52PM -0500

Hello....
 
Here is my final solution that i think works efficiently...
 
First it is better to do this:
 
I think that C++ and ADA and Object Pascal must make the data types
objects, and make datastructures objects and make IO objects etc. and
wrap those objects with a scalable reader-writer lock or transactional
memory because it is easy to do it this way, and the compiler designers
and implementors must test those objects correctly to ensure that they
work correctly, this will ensure a level of security that avoids race
conditions that is tolerable, so no need for pure functions and Mvars of
Haskel and Lisp.
 
And second you have to use set() and get() wrapped with a
scalable reader-writer lock or transactional memory to access the
properties of the object because it is esy to do it this way.
 
and third you can add also this:
 
About C++ and my following enhancement to it...
 
C++ must add properties that you can access only from the constructor
and can not be accessed from the methods of the object.
 
This way you will be able to implement more cleanly my following
implementation:
 
First you have to call a constructor that will put the global variables
as pointers for example in there respective queues..
 
And after that each method that wants to access a global variable will
take the global variable from the queue and copy it in a local
variable and work with it locally, and after that it will put
it back in its global queue , and other threads will block waiting
for the variables on there respective queues, it's like message passing
and it's like pure functions with Mvars in Haskel and this mechanism is
good and will avoid race conditions in Object oriented programming.
 
If you say to me that pure functions of Lisp and Haskel are pure
functions , but with my previous implementation you still can
by error forget to put your global variables that is
shared by threads in the properties that can not be accessed
by the object or in there respective global queues, i will say that
my implementation easy the job for us, because defining what is shared
and putting it in the properties that can not be accessed from the
object is easy and is as easy as making an error on sequential
programming, so in my opinion this level of security can be tolerated in
Object oriented programming without using Functional programming, other
than that we also have Transactional memory that is composable and easy
to use to solve our parallel programming problems in Object oriented
programming.
 
 
For Deadlocks use this:
 
Use Lock Hierarchies to Avoid Deadlock
 
http://www.drdobbs.com/parallel/use-lock-hierarchies-to-avoid-deadlock/204801163
 
 
Thank you,
Amine Moulay Ramdane.
bleachbot <bleachbot@httrack.com>: Dec 02 08:47PM +0100

bleachbot <bleachbot@httrack.com>: Dec 02 08:55PM +0100

bleachbot <bleachbot@httrack.com>: Dec 02 09:10PM +0100

bleachbot <bleachbot@httrack.com>: Dec 02 10:03PM +0100

bleachbot <bleachbot@httrack.com>: Dec 02 10:10PM +0100

bleachbot <bleachbot@httrack.com>: Dec 02 10:30PM +0100

bleachbot <bleachbot@httrack.com>: Dec 02 10:59PM +0100

bleachbot <bleachbot@httrack.com>: Dec 02 11:07PM +0100

udpbot <bleachbot@httrack.com>: Dec 02 11:07PM +0100

bleachbot <bleachbot@httrack.com>: Dec 03 12:16AM +0100

bleachbot <bleachbot@httrack.com>: Dec 03 12:33AM +0100

bleachbot <bleachbot@httrack.com>: Dec 03 12:38AM +0100

bleachbot <bleachbot@httrack.com>: Dec 03 12:52AM +0100

Ramine <ramine@1.1>: Dec 02 04:10PM -0500

Hello................
 
Here is how to implement pure functions of Haskel and Lisp in C++..
 
First you have to call a constructor that will put the global variables
as pointers for example in there respective queues..
 
And after that each method that wants to access a global variable will
take the global variable from the queue and copy it in a local
variable and work with it locally, and after that it will put
it back in its global queue , it's like message passing and
it's like pure functions with Mvars in Haskel and this mechanism is good
and will avoid race conditions in Object oriented programming.
 
 
For Deadlocks use this:
 
Use Lock Hierarchies to Avoid Deadlock
 
http://www.drdobbs.com/parallel/use-lock-hierarchies-to-avoid-deadlock/204801163
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Dec 02 06:38PM -0500

Hello...........
 
Fist solution:
 
I think that C++ and ADA and Object Pascal must make the data types
objects, and make datastructures objects and make IO objects etc. and
wrap those objects with a scalable reader-writer lock or transactional
memory, and the compiler designers and implementors must test those
objects correctly to ensure that they work correctly, this will ensure a
level of security that avoids race conditions that is tolerable,
so no need for pure functions and Mvars of Haskel and Lisp.
 
Or you can use this solution:
 
About C++ and my following enhancement to it...
 
C++ must add properties that you can access only from the constructor
and can not be accessed from the methods of the object.
 
This way you will be able to implement more cleanly my following
implementation:
 
First you have to call a constructor that will put the global variables
as pointers for example in there respective queues..
 
And after that each method that wants to access a global variable will
take the global variable from the queue and copy it in a local
variable and work with it locally, and after that it will put
it back in its global queue , and other threads will block waiting
for the variables on there respective queues, it's like message passing
and it's like pure functions with Mvars in Haskel and this mechanism is
good and will avoid race conditions in Object oriented programming.
 
If you say to me that pure functions of Lisp and Haskel are pure
functions , but with my previous implementation you still can
by error forget to put your global variables that is
shared by threads in the properties that can not be accessed
by the object or in there respective global queues, i will say that
my implementation easy the job for us, because defining what is shared
and putting it in the properties that can not be accessed from the
object is easy and is as easy as making an error on sequential
programming, so in my opinion this level of security can be tolerated in
Object oriented programming without using Functional programming, other
than that we also have Transactional memory that is composable and easy
to use to solve our parallel programming problems in Object oriented
programming.
 
 
For Deadlocks use this:
 
Use Lock Hierarchies to Avoid Deadlock
 
http://www.drdobbs.com/parallel/use-lock-hierarchies-to-avoid-deadlock/204801163
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Dec 02 06:33PM -0500

Hello....
 
Fist solution:
 
I think that C++ and ADA and Object Pascal must make the data types
objects, and make datatrctures objects and make IO objects etc. and wrap
of those objects with a scalable reader-writer lock or transactional
memory, and the compiler designers an implementors must test those
objects correctly to ensure that they work correctly, this will ensure a
level of security that avoids race conditions that is tolerable,
so no need for pure functions and Mvars of Haskel and Lisp.
 
Or you can use this solution:
 
About C++ and my following enhancement to it...
 
C++ must add properties that you can access only from the constructor
and can not be accessed from the methods of the object.
 
This way you will be able to implement more cleanly my following
implementation:
 
First you have to call a constructor that will put the global variables
as pointers for example in there respective queues..
 
And after that each method that wants to access a global variable will
take the global variable from the queue and copy it in a local
variable and work with it locally, and after that it will put
it back in its global queue , and other threads will block waiting
for the variables on there respective queues, it's like message passing
and it's like pure functions with Mvars in Haskel and this mechanism is
good and will avoid race conditions in Object oriented programming.
 
If you say to me that pure functions of Lisp and Haskel are pure
functions , but with my previous implementation you still can
by error forget to put your global variables that is
shared by threads in the properties that can not be accessed
by the object or in there respective global queues, i will say that
my implementation easy the job for us, because defining what is shared
and putting it in the properties that can not be accessed from the
object is easy and is as easy as making an error on sequential
programming, so in my opinion this level of security can be tolerated in
Object oriented programming without using Functional programming, other
than that we also have Transactional memory that is composable and easy
to use to solve our parallel programming problems in Object oriented
programming.
 
 
For Deadlocks use this:
 
Use Lock Hierarchies to Avoid Deadlock
 
http://www.drdobbs.com/parallel/use-lock-hierarchies-to-avoid-deadlock/204801163
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Dec 02 06:16PM -0500

Hello....
 
Here is another solution in Object oriented programming:
 
You can make all the objects type and datastructures etc. objects
and wrap those objects with a scalable reader writer lock and use
those objects as properties. This will reduce by much the risk of race
conditions. So no need for pure functions and Mvars of Haskel or Lisp.
 
 
Thank you,
Amine Moulay Ramdane.
RELIABLE VENDOR <no_email@invalid.invalid>: Dec 02 10:07PM

CLASSIC VENDOR WITH UNTRACEABLE SHIPPING AND PACKAGING METHOD. PAINKILLERS
AVAILABLE FOR SALE, ALONG SIDE MEDICAL MARIJUANA FOR DEPRESSION, CANCER,
CHRONIC PAIN, INSOMNIA ETC.
 
You can get a hold of me through email, text or call:
Email: topcaliberstocks@protonmail.com OR
Tel = Call/Text: +1(469) 249 2518
 
I am glad you are taking your time to go through my listing, and you should
be glad you did because you clicked on the right vendor, and you should be
rest assured that all your medical, pain, anxiety and addiction problems
will be taking care of without you stressing a muscle.
 
I will not try had to tell you what I am or what am not, instead, I will
put few names of the NUMEROUS medications I have below, and if you don't
see what you need please, contact me still with the name of the medication
you need and I will get back to you with every details you need.
 
#ayurvedic urea in powder
#Lemon Quaaludes 714
#Etaqualone powder Etaqualone pills
#Xanax 1 mg Upjohn footbals
#XANAX 1 mg (blue Ksalol)
#Xanax SR 2 mg (brand Upjohn)
# Xanax 2 mg (Pfizer LongBars)
#Valium 10 mg Bensedine
#AMBIEN (Zolpidem, Stilnox)
#Lorazepam 2.5 mg (Ativan)
#Clonazepam 2 mg (Rivotril)
#Nitrazeoam 5 mg (Nipam)
#Bromazepam 6 mg (Lexotan)
#Apaurine 10 mg (blue valium)
#aderall generic: amphetamine salt combo
#arimidex chemical name: anastrozole
30 pills
#adderall xr 10mg capsules 30 capsules
#codeine 30/500mg
#demerol (meperidine hcl) caps
#diazepam
#dilaudid
#soma -generic-
#ketalar injection
#ritalin
#flexeril (cyclobenzaprine) merck tabs
#hydrocodone 10mg/500mg 60tabs
#roxicodone 30mg (physicians tc)
#clonazepam (klonopin)
#fentanyl brand name: #duragesic 5-12 12.5 mcg/hr patches box
#oxycontin
#methadone
#seconal (chemical name-secobarbital)
#oxycodone-apap (wattson labs)
#vailum
#cialis
#vicoprofen (generic:hydrocodone-ibuprofen)
#hydrocodone-ibuprofen (brand name:vicoprofen)
#suboxone
#subutex
 
SERIOUS BUYERS ONLY. SAMPLE HUNTERS PLEASE EXCUSE
 
Do not hesitate to call me ANYTIME, and I will respond diligently. I will
also be open and glad to help you out with any medical problem you might be
facing and give you some advice.
 
The aim of every businessman is to maximize profit, and I am no exception.
But my second aim is to make sure all those who cannot get their hands on a
script to get what ever they need and be satisfied. Also, if there is a
medication you need but you are unable to walk into a store and get it
because of one reason or the other, then worry no more just contact me and
leave the rest to our conversation.
 
Again my contact is:
Email: topcaliberstocks@protonmail.com OR
Tel = Call/Text: +1(469) 249 2518
 
Thank you
Ramine <ramine@1.1>: Dec 02 02:56PM -0500

Hello....
 
About functional programming and object oriented programming..
 
I have continued to read about Lisp and Haskel functional languages,
and i have finally understood functional programming, in Lisp and
Haskel the functions are pure , that means that they don't use or call
global variables, but when you want to do mutability, you have
,like in message passing, to pass the local variable to an Mvar
in Haskel, it's like a queue, where the other threads must grap
this local variable and copy it in a local variable and
change it and put back this local variable in the queue for the other
threads to change it, so you will avoid race conditions in parallel
programming with this mechanism, but Mvar or the queues are still prone
to Deadlock or starvation. I have learned Lisp and Haskel and i have
noticed that to avoid the readability problem that i have spook about in
my previous post you have to decompose the many brackets with the defun.
 
In object oriented programming you can implement the Mvar of Haskel with
queues and you can avoid this way the problem of race conditions.
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Dec 02 05:07PM -0500

Hello,
 
About my previous enhancement to C++
 
If you say to me that pure functions of Lisp and Haskel are pure
functions , but with my previous implementation you still can
by error forget to put your global variables that is
shared by threads in the properties that can not be accessed
by the object or in there respective global queues, i will say that
my implementation easy the job for us, because defining what is shared
and putting it in the properties that can not be accessed from the
object is easy and is as easy as making an error on sequential
programming, so in my opinion this level of security can be tolerated in
Object oriented programming without using Functional programming, other
than that we also have Transactional memory that is composable and easy
to use to solve our parallel programming problems in Object oriented
programming.
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Dec 02 04:59PM -0500

Hello....
 
About my previous enhancement to C++
 
If you say to me that pure functions of Lisp and Haskel are pure
functions , but with my previous implementation you still can
by error forget to put your global variables that is
shared by threads in the properties that can not be accessed
by the object or in there repective global queues, i will say that
my implementation easy the job for us, because defining what is shared
and putting it in the properties that can not be accessed from the
object is easy and is as easy as making an error on sequential
programming, so in my opinion this level of security can be tolerated in
Object oriented programming without using Functional programming, other
than that we also have Transactional memory that is composable and easy
to use to solve our parallel progrmming problems in Object oriented
progrmming.
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Dec 02 04:30PM -0500

Hello.......
 
About C++ and my following enhancement to it...
 
To be able to implement pure functions with Mvars of Haskel more cleanly
in C++, C++ must add properties that you can access only from the
constructor and can not be accessed from the methods of the object.
 
This way you will be able to implement more cleanly my following
implementation:
 
Here is how to implement pure functions with Mvars of Haskel and Lisp in
C++..
 
First you have to call a constructor that will put the global variables
as pointers for example in there respective queues..
 
And after that each method that wants to access a global variable will
take the global variable from the queue and copy it in a local
variable and work with it locally, and after that it will put
it back in its global queue , and other threads will block waiting
for the variables on there respective queues, it's like message passing
and it's like pure functions with Mvars in Haskel and this mechanism is
good and will avoid race conditions in Object oriented programming.
 
 
For Deadlocks use this:
 
Use Lock Hierarchies to Avoid Deadlock
 
http://www.drdobbs.com/parallel/use-lock-hierarchies-to-avoid-deadlock/204801163
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Dec 02 04:03PM -0500

Hello....
 
Here is how to implement pure functions of Haskel and Lisp in C++..
 
Firt you have to call a constructor that will put the global variables
as pointers for example in there respective queues..
 
And after that each method that wants to access a global variable will
take the global variable from the queue and copy it in a local
variable and work with it locally, and after that it will put
it back in its global queue , it's like message passing and
it's like pure functions with Mvars in Haskel and this mechanism is good
and will avoid race conditions in Object oriented programming.
 
 
For Deadlocks use this:
 
Use Lock Hierarchies to Avoid Deadlock
 
http://www.drdobbs.com/parallel/use-lock-hierarchies-to-avoid-deadlock/204801163
 
 
Thank you,
Amine Moulay Ramdane.
Ramine <ramine@1.1>: Dec 02 03:10PM -0500

Hello,
 
I have explained to you in my previous post what is good in Lisp and
Haskel an how to implement in C++ the Mvar like in Haskel to make your
C++ methods pure like in Lisp and use like a message passing mechanism
with queues to avoid race conditions like in Lisp and Haskel.
 
 
Thank you,
Amine Moulay Ramdane.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.programming.threads+unsubscribe@googlegroups.com.

No comments: