John Chambers wrote:

| well if my 2p are worth at least 2p to you, do it in ansi C if you want
| anyone to use it. The advantages of portability and general
| comprehensability outweigh some fun features that nonstandard extensions
| may have. I like SNOBOL but I would avoid inflicting it on other people.

I'd prefer ansi C, mostly because it's the "least common denominator"
language that can be most easily included in the other C dialects and
the extensible languages like tcl, perl and python.



If I'm not mistaken, this is one issue that has been put to rest, and a consensus reached. The majority have spoken and all said pretty much the same thing... and I'm glad that even these recent posts support that decision.

So.. the parser is to be written in C.

What would everybody agree would be the next step? Remo's already researching API's... Sounds logical to me. If you were doing it yourself would establishment of an API (or the mere scaffolding of one) be the next step?

My next step is to reclaim the AlphabetSoup project on sourceforge which has been wrongly been changed to being owned by 'thistledown' instead of me, 'thistledowne'. Then I'll see about changing the name from AlphabetSoup to ABCp since there seems to be group support for that name.

//Christian M. Cepel aka thistledowne

--
||

Christian Marcus Cepel           | And the wrens have returned &
[EMAIL PROTECTED] icq:12384980 | are nesting; In the hollow of
371 Crown Point, Columbia, MO    | that oak where his heart once
65203-2202 573.999.2370          | had been; And he lifts up his
Computer Support Specialist, Sr. | arms in a blessing; For being
University of Missouri-Columbia  | born again. --Rich Mullins

To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html

Reply via email to