commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <>
Subject [jira] [Commented] (LANG-893) Default value for StrSubstitutor
Date Wed, 24 Jul 2013 16:23:48 GMT


Woonsan Ko commented on LANG-893:

Good to hear that. I'd like to try to create/upload a patch for this soon.

Regarding the default delimiter for the default value, I searched on the internet and found
this page:

Each programming language has its own solution:
For example, Freemarker and Velocity uses '!'. Javascript, Ruby and PHP use '||'. Perl uses
'//'. Groovy uses '?:' (which seems to be most similar to your suggestion). C# uses '??',
and so forth.

Personally, I started liking '||' followed by double or single quoted string after the research.
e.g, ${number||"N/A"} or ${number||'N/A'}. It seems most intuitive to me. ;-)

Anyway, selection of the default delimiter doesn't make any block here, so I can continue.
I'm open to any suggestions for the default delimiter string. Otherwise, I'd like to start
with '||' as default for now.


> Default value for StrSubstitutor
> --------------------------------
>                 Key: LANG-893
>                 URL:
>             Project: Commons Lang
>          Issue Type: Improvement
>          Components: lang.text.*
>    Affects Versions: 2.4
>            Reporter: Lauri Siltanen
>            Priority: Minor
> public static void main(String[] args) {
> 		String s = "The number of ${item} items currently available: ${number}";		
> 		String result = StrSubstitutor.replace(s, Collections.singletonMap("item", "monitor"));
> 		System.out.println(result);
> 	}
> This results in: "The number of monitor items currently available: ${number}".
> I'd need a default value for a placeholder that cannot be resolved.
> String result = StrSubstitutor.replace(s, Collections.singletonMap("item", "monitor"),
> -> "The number of monitor items currently available: N/A".

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message