Here's the opening post of that thread courtesy of The Wayback Machine (
http://web.archive.org/web/20081210195031/http://sourceforge.net/forum/message.php?msg_id=2300457).
Unfortunately the 6 replies don't seem to have been captured. However it
gives the date, time & subject so maybe someone else can use that to pull
out more.
{{{
*Have discoverd & started using LEO 2 days ago*
By: Nobody/Anonymous (nobody) - 2003-11-23 04:44
I really like the concept, literate prog, and i find it delivers.
I have easily made some code with it for some other languages and have
found that the "@first" directive is the key to output useable code in
unsupported languages.
...as example, for a BASIC language compiler:
->body of a "@file" header:
-----------------------------Snippet
@first $IFDEF LEOHEADER
@delims '
@c
$ENDIF
-----------------------------End of snippet
So this would enable a basic compiler to "jump" over the "true"
LEO-header-lines; wich gives you:
-----------------------Derived file begins with:
$IFDEF LEOHEADER <-conditionnal compilation directive
#@+leo-ver=4 <-these lines not compiled
#@+node:@file QParser005.INC
#@@first
#@delims '
'@@c
$ENDIF <-... Until here!
<rest of derived code file ... >
-----------------------end of snippet
The thing it does is mostly changing the comment symbol to " ' "
apostrophe... making comments parseable by a BASIC (or other language.)
The thing that I really like is the fact that LEO untangles my code if I
change it externally, in an IDE or editor of some kind!
hope this helps, if you have any tricks to share for adding compatibility /
productivity using LEO, please tell me!
--
bolt }}}
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
