> I've just finished reading Chapter 3 "Generators" of Thomas
> Christopher's book "Icon Programming Language Handbook"
>
> It's starting to look to me like (Un)Icon might be a bit too
> "idiomatic" for my liking or purposes.
Keep it as a casual learning exercise then. It will definitely help you think.
My first real project as an Icon newbie was a personal attempt at writing a
FORTRAN to C converter. In principle it's almost a no-brainer. However my
first code was clunky and slower than a wet weekend. I reached a point where
it wasn't going to get better and I dropped it.
When I came back to it later, I started again, somehow managed to do the Icon
"right", and the effectiveness and performance was much much better. I would
have even finished it if I didn't have to change jobs into a completely
difference sphere of computing! I wonder where that code is now.......
> At this initial stage of learning the language, I'm not interested in
> all the esoteric stuff, and layers upon layer of abstraction and
> obfuscation.
This puzzles me. I think what you really mean is the perhaps abstract nature,
focussing on the feature but not a big task that exploits and explains it? I
know that the main books tend to focus directly on the feature the current
section is talking about, without using it in a project. The treatment is
perhaps more mathematical than teaching a trade.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
