Prothon gets Major Facelift in Vers 0.1.0 [Prothon]

[Mark Hahn]

"gabor" <gabor at z10n.net> wrote

> yes, you can implement the needed mechanism in every language, but it's
> not always fun....

We'll just have to make sure it's fun in Prothon.  Maybe you'll have to
elaborate a little more on what you think is fun encapsulation documentation
and what isn't.

I myself think that putting underbars in front of every var like _var is not
fun.  Do you agree?

I also don't think declaring all vars as in "private var" is fun either, do
you?  If I did, I'd be using C++.

So to me, documenting the public vars makes the most sense.  They need some
explaining anyway.  So now the only question is, what is a fun and painless
way to document public vars.  It would be nice if it had these properties:

1) There should be some reward or lack of punishment for actually doing the
documentation.  I was thinking that Prothon could have some cool doc tool
that programmers would want to use that would choke and refuse to finish
without proper doc definitions.  Maybe the interpreter itself could even
give warnings.

2) The doc syntax should be painless, friendly, and intelligent enough so
human-added stuff is minimal.

Any ideas in this area would be greatly welcomed.  Implementing a half-baked
scheme would be as good as no scheme because it wouldn't be used.