![]() Pretty sure SU is built with ucrt, which is what the RubyInstaller (RI) version of Ruby 3.1 is built with. I’ll see if I can figure out what the current CRT dependency is Understanding RBS, Ruby's new Type Annotation System - Honeybadger Developer Blog.RBS: A New Ruby 3 Typing Language in Action | AppSignal Blog.GitHub - ruby/rbs: Type Signature for Ruby.rbs files, it will sniff out the headers of the files and decide if it’s a scrambled Ruby file or of it’s a Ruby 3.x type definition.įor more information about Ruby 3.x’s type definition files refer to the various documentation and articles out there. Upcoming version of SketchUp will be smarter in terms of handling. rbs files SketchUp would attempt to load that as a scrambled Ruby file, which off course won’t work. At the moment this would cause issues for SketchUp because when you perform a Sketchup.require it will look for. The type definition files aren’t something you’d distribute with your extension, but it is something you’d have along your. This presents a challenge for developers who would like to make use of this new type definition feature in Ruby. While we no longer offer this fileformat, it’s still found in older extensions that will continue to work and that users still use, so SketchUp continues to read these files for compatibility. Those of you that have been around for a while might recognize that as the file format for the old scrambled Ruby files that SketchUp previously offered. Ruby 3 introduces it’s own variant of this. If you have ever used TypeScript you’ll be familiar with Type Definition files. See the ruby-3.0.0 release post for more details. RubyInstaller-3.0.0-1 has been released! It features a whole bunch of great new features and improvements. This enables full Unicode character set for filesystem and environment variables and increases compatibility with other tools and operating systems. Ruby-3.0.0 finishes the transition to UTF-8 as the primary character encoding on Windows. It’s worth giving the release notes for Ruby 3.0 and 3.1 a read. This made it a lot easier to ensure that my new Fiddle implementation behaved the same as the old Win32 implementation. Then I split the old and new implementation into separate implementation files which I could replace upon load depending on SketchUp/Ruby version. If you are curious you can have a look at TT_Lib to get an idea of what I did: Bitbucket In order to aid this migration work I first wrote a set of TestUp tests against the existing code. I finally had to switch to Fiddle (which is a much better API btw.). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |