K
keith
I've heard so many different angles on this that I'd never pretend to be an
expert. Unless the compiler comes with a well delineated "fence" to
library functions forbidden for commercial exploitation, it's all a PITA to
me. I don't want to have to become a legal expert to know what's
allowed... or get caught with my pants down later.
Again, I'm talking from ignorance (the "sucker", who is not foreign to
this group doesn't seem to want to bite. It' smy understanding that the
normal 'C' stuff isn't in any way encoumbered, it's the GUI libraries
that seem to have a problem. ...so don't do GUI stuff in your critical
path. Why would you want to anyway. As Robert points out, a dynamically
linked library wouldn't expose your gonads.
Yes that is a seriously tough problem - any time you have cascading
dependencies on discrete decisions, it's a "hard" problem. Scheduling
of circuit board stuffing is another one.
The "traveling salesman" problem.
OK - there must be a way. I hope I can find it when needed.
It seems that you won't be blazing new territory. IBM's spent upwards of
$10B on Linux. I think I'm qualified to say that they're not giving
*anything* away.
BTW did you see my post on 3d partitioning of IC/PCBs? Just wondered
what you thought?
No. I missed it. If you can give me a reference... BTW, I'll be on the
road for the next week (visiting my 92YO mother), but I'll have my
ThinkPad and a cheezy hotel dial-up line, so...