I took a peek. That case statement isn't as wild as I was expecting
from your description....
How many descriptions are already in that case? I reckon barely 6 of those statements have seen more than one usage, and there are many more that never match. So its a losing position, especially given the limited icons its being used to deliver.
Is it giving you problems?
Its not a problem from a coding standpoint, just that it can't possibly contain
all the permutations and evolutions that come out of the BOM.
I'd imagine that using FTP to get your data is a lot more expensive
than the case statement.
I expect so, but its running in the background, no on demand so you don't get to see it.
structured format (even if it is XML...). I'd consider writing
a program in a language with a larger library to pick apart the
data.
I return to one of my recent observations, when all you have is a hammer, everything looks like a nail. BASH is my hammer. I don't have to many other skills hidden in the cupboard... touched on pascal before, but thats sooo rusty.. usually all I do, is assemble other bits of code to do what I need inside the bash script.
Not sure if I posted it here or FB now off hand, but my recent look at graphing
solution is related to similar data. The previous script is now fully functional, I stuck with my backhanded approach for now.
Spec
--- SuperBBS v1.17-3 (Eval)
* Origin: < Scrawled in blood at The Lower Planes > (21:3/101)