Sudarshan's excellent Master's degree work is in the main Unicon source
distribution so it may yet rise from stasis. It was fully implemented and
fairly heavily tested, although after Sudarshan graduated some bugs were
reported that I think aren't fixed.
It is under an #ifdef that is not turned on by default, but I am happy to
assist folks in trying it out or working on it further. I seek a student to
work on it and hope one comes along.
The feature will not get turned "on" by default unless or until (a) it
passes a certain level of testing and debugging, and (b) someone addresses a
certain lack of integration between it and the string scanning control
structure. At the moment it is a separate entity and one of the points of
Icon was to unify the pattern language into the main control structures as
compared with Snobol's separate-sublanguage model. I am willing to
compromise on Ralph Griswold's ideals but I also listen to counsel on such
matters and what I heard about Unicon patterns was that we need to figure
out how they relate to string scanning, which makes sense to me.
Cheers,
Clint
On Fri, Oct 21, 2011 at 6:39 AM, John Sampson <[email protected]> wrote:
>
> For a long time a paragraph was on the Unicon website about a paper
> by Sudarshan
> Gaikaiwari proposing a pattern data type in Unicon. Has this been given a
> decent burial
> or might it yet rise from the grave?
>
>
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
