top | item 1252205 (no title) patgarner | 16 years ago You're being overly dramatic. This has nothing to do with the normal use of layers of abstraction in your in architecture. discuss order hn newest statictype|16 years ago > This has nothing to do with the normal use of layers of abstraction in your in architecture.What's your definition of 'normal'?What if you abstract out your logic with a DSL that compiles down to iPhone native code? This is in violation of their terms of service.What if your DSL just generates C code? That also looks like a terms of service violation.Now what if that DSL is a yacc grammar for a network protocol or configuration file? Not an abnormal use anymore, is it?
statictype|16 years ago > This has nothing to do with the normal use of layers of abstraction in your in architecture.What's your definition of 'normal'?What if you abstract out your logic with a DSL that compiles down to iPhone native code? This is in violation of their terms of service.What if your DSL just generates C code? That also looks like a terms of service violation.Now what if that DSL is a yacc grammar for a network protocol or configuration file? Not an abnormal use anymore, is it?
statictype|16 years ago
What's your definition of 'normal'?
What if you abstract out your logic with a DSL that compiles down to iPhone native code? This is in violation of their terms of service.
What if your DSL just generates C code? That also looks like a terms of service violation.
Now what if that DSL is a yacc grammar for a network protocol or configuration file? Not an abnormal use anymore, is it?