https://github.com/trolldbois/ruby-haystack

haystack port to ruby. pitfall to ruby-ffi : 1) the generator outputs :pointer types which is basically equivalent to a void_ptr instead of a type_ptr . We cannot do automatic pointer type resolution.
https://github.com/trolldbois/ruby-haystack

Last synced: about 1 month ago
JSON representation

haystack port to ruby. pitfall to ruby-ffi : 1) the generator outputs :pointer types which is basically equivalent to a void_ptr instead of a type_ptr . We cannot do automatic pointer type resolution.

• Host: GitHub
• URL: https://github.com/trolldbois/ruby-haystack
• Owner: trolldbois
• Created: 2011-08-04T03:25:07.000Z (over 13 years ago)
• Default Branch: master
• Last Pushed: 2011-08-29T03:57:04.000Z (about 13 years ago)
• Last Synced: 2024-05-01T19:19:43.715Z (7 months ago)
• Language: Ruby
• Homepage:
• Size: 3.09 MB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README

Awesome Lists containing this project

README

        
Ruby port of the python-haystack memory search.

As long as there is no way to have a working TypedPointer in a StructLayout, 

that can be use to load Struct * on a generic fashion. there is no chance of

that port to be useful.

Can"t make Nice-FFI actually useful on Layout...