#815: Add a step for Configure:  auto::thread
-----------------------+----------------------------------------------------
 Reporter:  fperrad    |       Owner:  fperrad 
     Type:  patch      |      Status:  assigned
 Priority:  normal     |   Milestone:          
Component:  configure  |     Version:  1.3.0   
 Severity:  medium     |    Keywords:          
     Lang:             |       Patch:  new     
 Platform:  all        |  
-----------------------+----------------------------------------------------

Comment(by jkeenan):

 Replying to [ticket:815 fperrad]:

 François:  I commend you on your very thorough preparation of this patch.
 I appreciate the time and effort you take to get the tests right.

 It [http://smolder.plusthree.com/app/public_projects/report_details/24583
 passed all tests on Darwin/PPC].

 It [http://smolder.plusthree.com/app/public_projects/report_details/24585
 passed all tests on Linux/i386].

 The extent to which the tests cover the code can be seen
 [http://thenceforward.net/parrot/coverage/configure-build/config-auto-
 thread-pm.html here].

 Two small points, then two larger questions:

 1.  ''t/steps/auto_thread-01.t'' Line 20:  `s/crypto/threads/`

 2.  We will need to update ''MANIFEST'' before applying:  `perl
 tools/dev/mk_manifest_and_skip.pl`

 Larger questions:

 3.  Is there any way this patch could be done as part of an already
 existing configuration step?

 Personally, I like it the way it is and I wouldn't want to muddy up some
 other step just to save a few processes.  But I can bet that other
 contributors will raise that question, so I'm anticipating them.

 4.  While I'm satisfied with this addition, I'm no expert in threads.
 Does anyone else care to comment?

 Thank you very much.

 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/815#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to