> I hate to be the bearer of bad news, but I do believe I did indicate to your > first post on this subject that you should review the archives regarding > this issue. > > If you look back in the archives, we have been through this quite a few > times - there is a strong interest in keeping floating point numbers out of > VTL. > > To summarize the reasons, it's because many feel that because there is no > valid *presentational* use for floating point numbers, and that having that > support leads to the inclusion of business logic in the templates. > > Of course, you can always put business logic in templates if you work at it, > but its something that people, don't think should be encouraged. > > You can get around it if you must using tools. > > Now, regarding the VelocityValue, I personally don't think that it's > appropriate for use in the Velocity core. However, I do think that it is > interesting as a toolset that one could use in the context, so we should > explore that if you want. > > I (and I am sure others) do appreciate your efforts in this area, and it > would be great if we can find a way to make it available to the community.
Ok, well I'm not going to start any battles. If someone can let me know when Velocity will be extended to be able to support something like what I'm trying to do, with some kind of add-on module rather than changing the core as I have done, then I'd really appreciate it. I'll just absorb the 1.2 distribution in house and not concern myself with trying to keep up with the development effort, as it appears to be working fairly well for us as is. I was just trying to give back something. However, I do appreciate the effort that created Velocity in the first place and it certainly saved me the effort of coming up with something similar from scratch. Best Regards, Will Hartung ([EMAIL PROTECTED]) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
