On Mon, 5 Nov 2007, Ahmed S. Darwish wrote:I personally think string parsers are *much* better than the alternatives (which basically boil down to nasty binary interfaces) That's *MUCH* worse. Strings are nice. They aren't that complex, and as long as it's not a performance-critical area, there are basically no downsides. Binary structures and ioctl's are *much* worse. They are totally undebuggable with generic tools (think "echo" or "strace"), and they are a total nightmare to parse across architectures and pointer sizes. So the rule should be: always use strings if at all possible and relevant. If the data is fundamentally binary, it shouldn't be re-coded to ascii (no real advantage), but if the data is "stringish", and there aren't big performance issues, then keep it as strings. Linus -
| David Miller | Re: Slow DOWN, please!!! |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Jan Engelhardt | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
