instantiation

In Scala 2.10 apparently we're getting improved reflection. How will this impact lift-json, jerkson, sjson and friends? Furthermore, can we expect in the not too distant future a built-in JSON language feature a la Groovy's excellent GSON in Scala? The reason I ask is that I would dearly love to do: case class Foo(a: String, b: Int, bar: Bar) case class Bar(c: Int) val foo = Foo("hey", 10, Bar(23)) val json = foo.toJson without hoop jumping (i.e. boilerplate-ish prep work), even with arbitrarily complex object graphs. Perhaps I'm asking way too much, but one can always dream. Please shatter my

How we can instantiate class from it's name string in Ruby-on-Rails? For example we have it's name in database in format like "ClassName" or "my_super_class_name". How we can create object from it? Solution: Was looking for it myself, but not found, so here it is. Ruby-on-Rails API Method name = "ClassName" instance = name.constantize.new It can be even not formatted, we can user string method .classify name = "my_super_class" instance = name.classify.constantize.new Of course maybe this is not very 'Rails way', but it solves it's purpose. klass = Object.const_get "ClassName" about class

I'm designing a class that defines a highly complex object with a ton (50+) of mostly optional parameters, many of which would have defaults (eg: $type = 'foo'; $width = '300'; $interactive = false; ). I'm trying to determine the best way to set up the constructor and instance/class variables in order to be able to: make it easy to use the class make it easy to auto-document the class (ie: using phpDocumentor) code this elegantly In light of the above, I don't want to be passing the constructor a ton of arguments. I will be passing it a single hash which contains the initialization values, eg:

Say I want to init a UIView subclass with a String and an Int . How would I do this in Swift if I'm just subclassing UIView ? If I just make a custom init() function but the parameters are a String and an Int, it tells me that "super.init() isn't called before returning from initializer". And if I call super.init() I'm told I must use a designated initializer. What should I be using there? The frame version? The coder version? Both? Why? The init(frame:) version is the default initializer. You must call it only after initializing your instance variables. If this view is being reconstituted

This question already has an answer here: What does it mean to “program to an interface”? 32 answers Initializing an Interface? 2 answers Extending the question asked in Initializing an Interface? , we do instantiate an Interface while initialize it with implemented class. My question is why in the first place, we are instantiate it with the Interface? Why can't I directly instantiate it with implemented class? For eg. : Doc mydoc = new SimpleDoc(); Where Doc is interface and SimpleDoc is implementing it. What is the problem with SimpleDoc mydoc = new SimpleDoc(); Where this will fail? It's

In Unity 5 using c# on line 35 of my PlayerMovement class I have this error: Error CS0120 An object reference is required for the non-static field, method, or property 'GameManager.completeLevel()' PlayerMovement Class: using System.Collections; using System.Collections.Generic; using UnityEngine; public class PlayerMovement : MonoBehaviour { public GameObject deathParticals; public float moveSpeed; private Vector3 spawn; // Use this for initialization void Start () { spawn = transform.position; moveSpeed = 5f; } // Update is called once per frame void Update() { transform.Translate(moveSpeed

Is it ok to instantiate an object in a View before passing it to a partial? <%= render :partial => "trade_new", :locals => {:trade=>Trade.new("e", "b") } %> Or is better to instantiate any objects in the Controller as instance variables: @trade = Trade.new("e", "b") and then pass the instance variable to a partial in the view like this: <%= render :partial => "trade_new", :locals => {:trade => @trade } %> My guess is it's better to instantiate new objects in the controller to avoid duplication - such as in a case where multiple templates may need to pass this new object to a partial from the