Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

First of all I'm developing a parser for an XML-based format for 3D graphics called XGL. But this question can be applied to any situation when you have fields in your class that are optional i.e. the value of this field can be missing.

As I was taking a Scala course on coursera there was an interesting pattern when you create an abstract class with all the methods you need and then create a normal fully functional subclass and an "empty" singleton subclass that always returns false for isEmpty method and throws exceptions for the other ones.

So my question is: is it better to just assign null if the optional field's value is missing or make a hierarchy described above and assign it an empty singleton implementation?

share|improve this question
1  
You're referring to the Null Object Pattern: en.wikipedia.org/wiki/Null_Object_pattern –  Baqueta Nov 23 '12 at 9:45
add comment

2 Answers

up vote 2 down vote accepted

I also attended the same Scala course and I agree with e-i-s that you should use the Option[T] type for implementing an optional field. Here are some more ideas.

The pattern involving

  • a trait with method isEmpty
  • several classes or objects extending the trait
  • a unique object whose method isEmpty always returns true

is also used to implement sequence-like immutable structures such as lists, streams, and so on.

Compare:

  1. An Option[T] type containing the values Some(t), for each value t in T, and the additional value None.
  2. A List[T] type containing objects built from two subclasses (and their respective constructors) Cons[T](h: T, t: List[T]) and Nil: these represent immutable lists whose elements have type T. Note that here the method Nil.isEmpty returns true.

None indicates the absence of a value, while Nil indicates an empty list.

So an optional value None is not the same as an empty list Nil.

NOTE

If you need to test if an optional value is defined or not you can use the isEmpty method of the Option type, or pattern matching:

class MyClass(f: Option[String])
{
  val field = f
}

and then, to test if the field of an instance obj of MyClass is defined:

if (obj.field.isEmpty)
{
}
else
{
}

or

obj.field match
{
  case Some(s) => /* do something with s */
  case None    => /* ... */
}
share|improve this answer
add comment

If your implementation is in Scala, it is idiomatic to use the Option[T] type.

share|improve this answer
1  
Wow, that's really helpful. I'm also using this code from java app. How will java work with Option[T]? Should I provide some additional methods? Because with null it's simple: if (object.field() != null) {...} –  Uko Nov 23 '12 at 10:03
1  
I'm not sure, but I think you can call Option's isEmpty from Java to check if there's any value (the equivalent to if (object.field() == null) { ... }). But I haven't tried this. –  MisterMetaphor Nov 23 '12 at 10:25
2  
Using Option core methods isEmpty()/isDefined() and get() works perfectly fine from Java. –  David Pierre Nov 23 '12 at 10:50
    
And you have Option.option2Iterable, so you can use Options in enhanced for-loops. –  Landei Nov 23 '12 at 14:44
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.