3 ms·

ah nice , similar to what I expected. Its also very nice to see a new way of doing things. I will have to look more deeply into your implementation. I really ho

by kilon 13y ago

ah nice , similar to what I expected. Its also very nice to see a new way of doing things. I will have to look more deeply into your implementation. I really hope you keep up with this and not abandon it. I would love to have an objective C alternative. Is there support "out of the box" for obj c libraries , or wrappers will be needed to do so ? I see you support the to: message for loops, is there also a do: message for iterations ? I really prefer it instead of for loops :) I see the syntax really looks like smalltalk and that for me is a huge plus compared to Objective C, well done and as I said I really hope you keep working on this. I am definitely going to try it :)

mpweiher 13y ago
"obj c libraries" Any library in the image can be accessed via messaging without wrappers, that's the "peer" idea. C functions currently have to be wrapped, one of the reasons I did an Objective-C wrapper for CoreGraphics: https://github.com/mpw/MPWDrawingContext https://github.com/mpw/MPWDrawingContext The REPL / command-line script interpreter also has a convenience method for loading frameworks, so `context loadFramework:'AppKit' will load the AppKit and also parse the scripting-bridge definitions so you have access to constants. Combined with the ability to drop back into the REPL, this has made it possible for me to trivially create custom shell, for example pdfsh <filename> loads a PDF into memory and then drops me at the command prompt with an object representing the PDF bound to the variable `pdf`. "iteration" Most normal Smalltalk collection/block iteration protocol is supported, so #to:do: is just shorthand for first #to: , creating an Interval, and then #do: iterating that interval. In addition to the ones taking a block argument, you also get the equivalent ones taking a message.
- kilon 13y ago
  very well done. Its seems you have created something that has a lot of potential. Being able to use obj c libraries out of the box and yet use smalltalk syntax is a huge win for me. I only hope the best for your project :)

by kilon 13y ago

mpweiher 13y ago

"obj c libraries" Any library in the image can be accessed via messaging without wrappers, that's the "peer" idea. C functions currently have to be wrapped, one of the reasons I did an Objective-C wrapper for CoreGraphics: https://github.com/mpw/MPWDrawingContext https://github.com/mpw/MPWDrawingContext The REPL / command-line script interpreter also has a convenience method for loading frameworks, so `context loadFramework:'AppKit' will load the AppKit and also parse the scripting-bridge definitions so you have access to constants. Combined with the ability to drop back into the REPL, this has made it possible for me to trivially create custom shell, for example pdfsh <filename> loads a PDF into memory and then drops me at the command prompt with an object representing the PDF bound to the variable `pdf`. "iteration" Most normal Smalltalk collection/block iteration protocol is supported, so #to:do: is just shorthand for first #to: , creating an Interval, and then #do: iterating that interval. In addition to the ones taking a block argument, you also get the equivalent ones taking a message.

kilon 13y ago
very well done. Its seems you have created something that has a lot of potential. Being able to use obj c libraries out of the box and yet use smalltalk syntax is a huge win for me. I only hope the best for your project :)