Nick Antonaccio napsal(a): > Hi Paavo, > > Just tonight, a reader from my site wrote to say that in the past, all =20 > the documentation he had previously read had led him to misunderstood =20 > the syntax of a simple 'if expression, originally thinking that the =20 > conditional evaluation needed to be placed in brackets (which made =20 > every condition always evaluate to true...). Even things like that =20 > can be tripping blocks for newcomers, so I agree that obfuscated code =20 > can be totally unfathomable. > > With that said, it is important to recognize common code patterns and =20 > Rebolisms that are fast and short in expression, even if they're hard =20 > to read at first. I don't know that common (more difficult to read) =20 > syntax necessarily needs to be avoided and replaced with obvious =20 > patterns. (If they're common, they _should_ be internalized). =20 > Instead, what I missed in the beginning with Rebol was more documented =20 > examples ... I mean the kind of detailed, line by line documentation =20 > needed to understand each expression, as well as the overall structure =20 > of a script. Hi,
dunno if following might help, but Carl once wrote suggested REBOL code formatting, and it is part of REBOL/Core documentation. It really helps if guys keep some rules, e.g. I absolutly hate, if someone uses something like: hello: func [ greeting ] [ print greeting ] :-) Here's link for suggested code patterns (although I know you have something a bit different in mind with code patterns probably): http://www.rebol.com/docs/core23/rebolcore-5.html#section-5 Petr -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
