BIND segway -> python -> first-class ports -> parsing

[Teske, Devin]

On Dec 9, 2013, at 10:17 AM, Teske, Devin wrote:

> 
> On Dec 9, 2013, at 9:27 AM, Teske, Devin wrote:
> 
>> 
>> On Dec 9, 2013, at 3:21 AM, George Mitchell wrote:
>> 
>>> On 12/09/13 00:39, Teske, Devin wrote:
>>>> [...]
>>>> But keep in mind...
>>>> 
>>>> The real power is not in shell, the real power is in POSIX. I have the supreme
>>>> pleasure of having developed C programs that can compile on:
>>>> 
>>>> + Windows using MinGW
>>>> + Mac OS X using ... gcc
>>>> + Mac OS Classic using SIOUX
>>>> NB: Simple Input/Output User eXchange
>>>> + Linux, Unix, BSD, AIX, OSF1, Amiga, etc.
>>>> 
>>>> All with a single source package. It's the power of POSIX.
>>>> 
>>>> So whenever I've made a choice to target "/bin/sh" as a platform, it's
>>>> always *only* ever been based on the decision of "reach".
>>>> 
>>>> Shell quite often doesn't cut it. Prior to shell, I spent my time trying
>>>> building libraries used to abstract higher functionality for cross-platform
>>>> compatibility. And, until now, that's primarily been in C -- shell is only a
>>>> recent excursion because I feel I've *finally* nailed the right recipes for
>>>> that.
>>>> 
>>>> I'm actually a bit worried that Python and Lua don't have the reach that C does,
>>>> let alone shell.
>>>> 
>>> 
>>> +1 to a well-reasoned and insightful post.
>>> 
>>> What are your thoughts on the other part of Mr. Perlstein's concern: the
>>> lack of what I would like to call a Grand Unified Schema?  Perhaps such
>>> a thing belongs in POSIX as well, as it would be intriguing to be able
>>> to write tools (in whatever language) that could rely on uniformly
>>> parseable data (i.e. sizes always known to be in eight-bit bytes, text
>>> in UTF-8 [let's say], time in seconds, numbers in decimal without
>>> commas, key-value pairs in a specified format, consistent meaning for
>>> key names).                                                 -- George
>> 
>> Hi George,
>> 
>> I'm glad you asked.
> 
> My experience tells me that 90% of the Grand Unified Schema is adapting
> a single interface so that the following two issues are dealt with:
> 
> [snip]
> 
> 	1. Centralized parsing library
> 
> 	2. Centralized mangling library
> 

#1 I've conceptualized into code as "libfigpar".

For #2, I'm thinking something similar, but libfigman (for "Con[fig]uration [Man]gler")

;D
-- 
Devin

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.