January 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Happy new year, to all of you!!!

by Sean P. DeNigris

Happy New Year, Pharo Community!!! Your friend and colleague, Sean -- View this message in context: http://forum.world.st/Happy-new-year-to-all-of-you-tp4661573p4661606.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 1, 2013

Re: [Pharo-project] Change Log link

by Marcus Denker

On Jan 1, 2013, at 2:33 PM, âking <rkingdesk(a)sharpsaw.org> wrote: > The link under "Change Log" on > http://www.pharo-project.org/pharo-download/beta-2-0 > points to: > http://code.google.com/p/pharo/wiki/ActionsInPharo2 (a 404) > Should be: > http://code.google.com/p/pharo/wiki/ActionsInPharo20 (I think) I fixed the link, thanks, Marcus

Jan. 1, 2013

[Pharo-project] Change Log link

by âking

The link under "Change Log" on http://www.pharo-project.org/pharo-download/beta-2-0 points to: http://code.google.com/p/pharo/wiki/ActionsInPharo2 (a 404) Should be: http://code.google.com/p/pharo/wiki/ActionsInPharo20 (I think) Thanks! ââ

Jan. 1, 2013

[Pharo-project] Remote Pair Programming

by âking

Hi! 2013 is rking's "Year of Smalltalk" (I'm going to stop admiring it from afar and actually get good with it). One piece I was wondering about: is there any handy remote pairing solution other than having one of the two use VNC? VNC has its disadvantages, one being that the non-local user is rather lagged compared to the local one. For Ruby remote pairing, we use tmux and vim and shell stuff, and it works well, so I'm looking for a good Smalltalk solution. ââ P.S.: If anyone wants to pair, let me know, I'd love to jump in on whatever code you're writing.

Jan. 1, 2013

Re: [Pharo-project] Native Boost Basics: passing char* buffer

by Igor Stasenko

On 1 January 2013 09:39, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > testPharoBuffer > "self new testPharoBuffer " > | buf addr addr2 | > buf := String new: 100000. > addr := buf asNBExternalString. > addr2 := ( NativeBoost allocate: 256 ). > self testPharoBuffer: addr . " or use addr2, both of it does not > work" > Transcript cr; show: buf. > > > have tried "addr readString" / on addr2 .. too > > Need to understand how to pass a memory location to the dll function stack > and get back what is written to the memory in Pharo in a more general sense. > > Hmm.. Did you changed the signature? self nbCall: #( int readAndWritePipe( void * buf ) ) module: 'TestPharo.dll' So, if this a String (a variable-byte object) , a function will receive a pointer to its first byte, and if its address (NBExternalAddress) then a pointer passed to function will be equal to that address. > > On Tue, Jan 1, 2013 at 12:13 PM, S Krish <krishnamachari.sudhakar(a)gmail.com> > wrote: >> >> I am trying to work with memory addresses back n forth.. >> >> Simple case of char* buffer that needs to be filled in by dll . Buffer >> does not change in Pharo after the call. Am I missing something here.. >> >> The memory address that is printed out does not match what I see in Pharo >> / infact the address does not change at all... for repeated call invoked >> from debugger. >> >> C Code: >> >> DLLEXPORT int readAndWritePipe(char* outBuf ) >> { >> system("Echo readAndWritePipe" ); >> debugPrintf ( "readAndWritePipe: %d \n" , &outBuf , 1046 ); >> memcpy ( outBuf , "Testing123\0" , 11) ; >> return 0; >> } >> >> void debugPrintf ( char* logString, int intArg , char* strArg, int size ) >> { // can redirect as needed to logger end point.. >> FILE * logFile = fopen( "c:\\temp\\writePipes.log" , "a" ); >> char* buf = (char*) calloc( sizeof(char) , size ); >> sprintf( buf, logString , intArg , strArg ); >> fputs(buf , logFile ); >> fclose(logFile); >> } >> >> Pharo: >> >> testPharoBuffer: buf >> >> <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: >> errorCode > >> ^ self nbCall: #( int readAndWritePipe( String buf ) ) module: >> 'TestPharo.dll' >> >> >> testPharoBuffer >> "self new testPharoBuffer " >> | buf addr addr2 | >> buf := String new: 100000. >> addr := buf asNBExternalString. >> addr2 := ( NativeBoost allocate: 256 ). >> self testPharoBuffer: addr . " or use addr2, both of it does not >> work" >> Transcript cr; show: buf. >> > > -- Best regards, Igor Stasenko.

Jan. 1, 2013

Re: [Pharo-project] Native Boost Basics: passing char* buffer

by S Krish

Thanks, char* and void* works like a charm...

Jan. 1, 2013

Re: [Pharo-project] Native Boost Basics: passing char* buffer

by S Krish

testPharoBuffer "self new testPharoBuffer " | buf addr addr2 | buf := String new: 100000. addr := buf asNBExternalString. addr2 := ( NativeBoost allocate: 256 ). self testPharoBuffer: addr . " or use addr2, both of it does not work" Transcript cr; show: buf. have tried "addr readString" / on addr2 .. too Need to understand how to pass a memory location to the dll function stack and get back what is written to the memory in Pharo in a more general sense. On Tue, Jan 1, 2013 at 12:13 PM, S Krish <krishnamachari.sudhakar(a)gmail.com>wrote: > I am trying to work with memory addresses back n forth.. > > Simple case of char* buffer that needs to be filled in by dll . Buffer > does not change in Pharo after the call. Am I missing something here.. > > The memory address that is printed out does not match what I see in Pharo > / infact the address does not change at all... for repeated call invoked > from debugger. > > C Code: > > DLLEXPORT int readAndWritePipe(char* outBuf ) > { > system("Echo readAndWritePipe" ); > debugPrintf ( "readAndWritePipe: %d \n" , &outBuf , 1046 ); > memcpy ( outBuf , "Testing123\0" , 11) ; > return 0; > } > > void debugPrintf ( char* logString, int intArg , char* strArg, int size ) > { // can redirect as needed to logger end point.. > FILE * logFile = fopen( "c:\\temp\\writePipes.log" , "a" ); > char* buf = (char*) calloc( sizeof(char) , size ); > sprintf( buf, logString , intArg , strArg ); > fputs(buf , logFile ); > fclose(logFile); > } > > Pharo: > > testPharoBuffer: buf > > <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: > errorCode > > ^ self nbCall: #( int readAndWritePipe( String buf ) ) module: > 'TestPharo.dll' > > > testPharoBuffer > "self new testPharoBuffer " > | buf addr addr2 | > buf := String new: 100000. > addr := buf asNBExternalString. > addr2 := ( NativeBoost allocate: 256 ). > self testPharoBuffer: addr . " or use addr2, both of it does not > work" > Transcript cr; show: buf. > >

Jan. 1, 2013

Re: [Pharo-project] Native Boost Basics: passing char* buffer

by Igor Stasenko

On 1 January 2013 07:43, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > I am trying to work with memory addresses back n forth.. > > Simple case of char* buffer that needs to be filled in by dll . Buffer does > not change in Pharo after the call. Am I missing something here.. > > The memory address that is printed out does not match what I see in Pharo / > infact the address does not change at all... for repeated call invoked from > debugger. > > C Code: > > DLLEXPORT int readAndWritePipe(char* outBuf ) > { > system("Echo readAndWritePipe" ); > debugPrintf ( "readAndWritePipe: %d \n" , &outBuf , 1046 ); > memcpy ( outBuf , "Testing123\0" , 11) ; > return 0; > } > are you sure you want to print an address of argument (&outBuf) instead of argument value (outBuf - which is a pointer value passed to function) ? Because &outBuf, will always be a location on stack where the value stored. And sure thing, when you call that function from simple short test app, it will be always same, since nothing interferes with stack. > void debugPrintf ( char* logString, int intArg , char* strArg, int size ) > { // can redirect as needed to logger end point.. > FILE * logFile = fopen( "c:\\temp\\writePipes.log" , "a" ); > char* buf = (char*) calloc( sizeof(char) , size ); > sprintf( buf, logString , intArg , strArg ); > fputs(buf , logFile ); > fclose(logFile); > } > > Pharo: > > testPharoBuffer: buf > > <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: > errorCode > > ^ self nbCall: #( int readAndWritePipe( String buf ) ) module: > 'TestPharo.dll' > > > testPharoBuffer > "self new testPharoBuffer " > | buf addr addr2 | > buf := String new: 100000. > addr := buf asNBExternalString. > addr2 := ( NativeBoost allocate: 256 ). > self testPharoBuffer: addr . " or use addr2, both of it does not > work" > Transcript cr; show: buf. > String type in signature makes a copy of string on stack + adds null-terminating character, and then pushing the pointer on stack as argument to function. So, it is more like 'pass by value-copy' argument. If you want to do 'pass by reference', just use 'void *' (or char* ) in function signature, but then make sure you null-terminate stuff there by yourself, if needed. String type converter is more for convenience to avoid dealing with null-terminating chars every time. But sure thing, if you need to pass a pointer to buffer, where function will store something ,you should not use it. -- Best regards, Igor Stasenko.

Jan. 1, 2013

[Pharo-project] Native Boost Basics: passing char* buffer

by S Krish

I am trying to work with memory addresses back n forth.. Simple case of char* buffer that needs to be filled in by dll . Buffer does not change in Pharo after the call. Am I missing something here.. The memory address that is printed out does not match what I see in Pharo / infact the address does not change at all... for repeated call invoked from debugger. C Code: DLLEXPORT int readAndWritePipe(char* outBuf ) { system("Echo readAndWritePipe" ); debugPrintf ( "readAndWritePipe: %d \n" , &outBuf , 1046 ); memcpy ( outBuf , "Testing123\0" , 11) ; return 0; } void debugPrintf ( char* logString, int intArg , char* strArg, int size ) { // can redirect as needed to logger end point.. FILE * logFile = fopen( "c:\\temp\\writePipes.log" , "a" ); char* buf = (char*) calloc( sizeof(char) , size ); sprintf( buf, logString , intArg , strArg ); fputs(buf , logFile ); fclose(logFile); } Pharo: testPharoBuffer: buf <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode > ^ self nbCall: #( int readAndWritePipe( String buf ) ) module: 'TestPharo.dll' testPharoBuffer "self new testPharoBuffer " | buf addr addr2 | buf := String new: 100000. addr := buf asNBExternalString. addr2 := ( NativeBoost allocate: 256 ). self testPharoBuffer: addr . " or use addr2, both of it does not work" Transcript cr; show: buf.

Jan. 1, 2013

Re: [Pharo-project] Happy new year, to all of you!!!

by S Krish

All, Happy Smalltalking all the way through the new year and the decade ahead. All the best in every way, prosperity is most important that can enable more smalltalk, a virtuous cycle of give and take in the year ahead. On Tue, Jan 1, 2013 at 5:38 AM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > I wish you a Happy Phaoring for 2013! > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Jan. 1, 2013