In article <p05200f0bba23a385de61@[192.168.0.2]>,
 [EMAIL PROTECTED] (Emmanuel. M. Decarie) wrote:

> À (At) 18:07 -0500 14/12/02, Chris Nandor écrivait (wrote) :
> >Could you search your system headers for "keyReplyPortAttr"?
> 
> Hmm, not sure what you are saying here. I just know basic C and I'm 
> not familiar with the Carbon framework. Where are my system headers?
> 
> I tried that though:
> 
> % grep -r "keyReplyPortAttr"  /System/Library/Frameworks/*
> 
> But it take forever to run. If you give me more details, I'll try again.

Yes, it could take forever.  :-)  I am not sure how to better narrow it 
down, though.  Maybe use find(1) to look for *.h files.


> >If you can't find it, try (in Carbon.h, or AppleEvents.xs):
> >
> >    #define keyReplyPortAttr 'repp'
> 
> Ok, in Carbon.h, in the beginning of the file:
> 
> #ifndef  MAC CARBON H
> #define  MAC CARBON H
> #define keyReplyPortAttr 'repp'
> 
> >See if that works.
> 
> Well it pass most of the tests (btw, these tests are very funny)

Good, and :).


> t/Carbon......................._ComponentCacheableInitialize
> t/Carbon.......................ok

As noted in a previous post, some Components when initialized or used or 
something decide to emit text to STDERR (hopefully, it's STDERR, not 
STDOUT!).  I consider this behavior broken on behalf of the component, 
though I suppose I could be wrong.  But you should see this any time you run 
anything on the command line that loads in components, such as osascript(1).

So basically, I don't know I can do anything to quiet that 
"_ComponentCacheableInitialize".


> MacPerl/t/MacPerl..............ok 3/13 ComponentCacheableInitialize
> Argument "10.1.2" isn't numeric in numeric ge (>=) at 

Fixed for 0.03.


> MacPerl/t/MacPerl.t line 40.
> MacPerl/t/MacPerl..............ok 10/13#     Failed test 
> (MacPerl/t/MacPerl.t at line 88)
> #          got: '2'
> #     expected: '3'
> MacPerl/t/MacPerl..............ok 12/13# Looks like you failed 1 tests of 13.
> MacPerl/t/MacPerl..............dubious
>          Test returned status 1 (wstat 256, 0x100)
> DIED. FAILED test 11
>          Failed 1/13 tests, 92.31% okay

Weird.  Are you sure you clicked Cancel?


> Processes/t/Processes..........ok
>          2/6 skipped: No parent

Odd.  You ran this on the local machine from Terminal.app?

-- 
Chris Nandor                      [EMAIL PROTECTED]    http://pudge.net/
Open Source Development Network    [EMAIL PROTECTED]     http://osdn.com/

Reply via email to