On Tue, 24 Dec 2013 07:56:02 -0800 (PST)
"Edward K. Ream" <[email protected]> wrote:
> It *will* be possible to use @auto instead of @file in many cases.
> At present, the *new* importer produces::
>
> if 0:
> @others
> <<class testClass1>>
>
> #<<define dump>> <----- a light sentinel
So will @auto still have close to zero impact on collaborated files? A
little one time white space jiggling might be acceptable, but the above
would be optional, right? I'm not that fussy about what gets placed
under @others vs. section references (I never use them), but I don't
want to inflict
#<<define dump>>
def dump():
...
on non-Leo users, comments that state the obvious are irritating, and
people will delete them.
So if the '#<<define dump>>' construct is optional, fine - otherwise
I'd wonder if we need two flavors of @auto, either with a new @name or
a flag, one for zero impact, and the other for more @file like behavior.
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
