Ah, I missed some earlier talk. I saw your splurb apeiros and thought it could be an openstruct or struck as well.
Do you guys think there is a point when a library is overly documented with inline documentation?
Maybe an initial flow document or something that would say this happens with this, for more information learn xyz? I personally like how AWS did their SDK docs with example inputs and the expected output and what the struct or hash looked like
Speaking of vagrant, has anyone here tried using a mixture of Vagrant and OpenStack using the vagrant-openstack-provider and a HEAT template to create volumes and attach them to nodes without having to create volumes before hand?
Hey everyone. Has anyone worked with JRuby and Ant tasks? I'm not sure what I would need to do with my Rake task to make it so I can include the Manifest into my JAR file.
@hays I usually just run the RubyInstaller for Windows and it took care of the upgrade .
From what I understand, its to allow a function to hold off on executing the rest of its code, and do what's in the do...end block, whether that be execute other code, or assign variables.
to see if there were any other methods that needed to be evaulated inside that tag