David Abrahams wrote: > Joel de Guzman <[EMAIL PROTECTED]> writes: > >> Paul A Bristow wrote: >> >>> Another feature that caused me some grief is that you can't simply >>> have ]s in comments - that ends the comment. It does what it says on >>> the can, but you can't quickly comment out lines as you can with C++ >>> // >> Fixed. Now you can nest comments and blocks inside comments > > I'm afraid you can't, because the parsing is too simplistic: > > qbk semantics > ------------------- --------- > [^foo *bar 5]*] <tt>foo <bold>bar 5]</bold></tt> > > [/[^foo *bar 5]*]] ] > ^ > +--- closes the comment > > IMO if we want to be able to reliably comment out regions, we either > need to actually parse the interior of the comment just as though it > was regular QBK (in which case you can't comment out > syntactically-invalid stuff) or we need a region terminator that's > reasonably distinctive. IOW, ']' doesn't cut it.
This will not be a problem once we make unescaped [ and ] illegal in Qbk (including inside simple style markups). Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
