> Just wondering if a method would be more explicit---e.g., something like
>
> Schedule s = originalSchedule.until(d);
>
> might be more readable than
>
> Schedule s(originalSchedule, d);
>
> Thoughs?
I considered this option and don't have a strong preference between the two.
I favored the constructor just because the QuantLibAddin mapping would
have been a constructor in both cases (as for all methods/functions
returning objects).
Feel free to change it as you prefer
ciao -- nando
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev