> So I find all this discussion about "why would you do that" a little
> suspect... we don't know the business requirements that drive these
> choices. What I do know is that it is distinctly plausible to emulate
> those fixed-length/blank-padded strings in C++, so it's probably not
> much harder to do in .Net
That's irrelevant. What's important is that people shouldn't focus on
how to implement a bad solution because it's
apparently hard to implement, they should focus on finding a better solution
first. The solution proposed is simply silly when you
look at the 3Gl's today. You might say it's doable in C++, but it requires
inserting 0's inside to string, so you need manipulation
code anyway, plus it's very restrictive, as you can't deal with strings which
are 1 character longer.
Nothing personal topicstarter, but it's decisions like this 'solution'
which doesn't work in .NET which gives software
engineering still a bad name and why people are sceptical about what they might
get for the big pile of cash they're willing to pay.
So if a person asks if he can do these kind of weird things in .NET I
really want to know WHY as it's severely relevant for
me to even consider the question serious, no matter how big the pile of cash is
that's apparently at stake.
Oh, and bank software might be old in some banks, but there's also bank
software which costs less than a million$ which is
modern and ready to use. Just that it's being old and runs on a dinosaur
machine doesn't make it excellent stuff which can't be done
today.
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
