Passing null arguments using the undefined variable called something like nullArg does not seem to work for me any more

Geoff Shuetrim <[email protected]>
Newsgroups gmane.comp.web.freemarker.user
Message-ID <CAB13hhajq-R3qLgWJ2j3o52V5jDjcE8cS=mJPi_+KYF+RLoLSg@mail.gmail.com>
I have upgraded to use Freemarker 2.3.17 and am finding that passing null
arguments using the undefined variable nullArg does not seem to work for me
any more.  In particular I am finding that Freemarker cannot match up a
function call where some of the parameters have null values (given as
nullArg variables that have not been previously defined) to any existing
method signature.  Is there some change that I should be adapting my
templates to?

Regards

Geoff S

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2

_______________________________________________
FreeMarker-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freemarker-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.