nimforum mirror - Simple Python-like class macro and some python-like procedures (print, input, range, others)

Tiberium (orginal) [2017-08-25T17:51:32+02:00] view original

I've implemented some simplest Python functions and very simple "class" macro (which doesn't and wouldn't support inheritance). https://github.com/Yardanico/nimpylib - check example2.nim for classes.

Yeah, code isn't the best - this is mainly due to the nature of Python (dynamic-typing), for example:

"range(5)" - here 5 is a position where range stops

"range(1, 5)" - 1 here is a position where range starts

Simplest example of class macro usage:

import pylib

type HelloWorld = ref object
  name: string

class HelloWorld(object):
  def init(self, name):
    self.name = name
  
  def greet(self):
    print("Hello,", self.name, sep = "\n")

let c = newHelloWorld("Daniil")
c.greet()

Udiknedormin (orginal) [2017-08-26T23:56:50+02:00] view original

Thanks to you I noticed there are finally proper AST nodes for doc-comments (one of the great features in Rust I hated Nim doesn't have). Yay!

Back to your module. I have mixed feelings...

class -- I like it quite a lot, good macro. I've already seen a similar one in the past (just after I started coding the same functionality, by the way) but the syntax was more Nim-like. Which is good as your way is easier to port from Python. Hell, for simple cases copy-pasting is enough!

range -- is a bit unobvious. In loops, it works like in Python3 (iterator approach). Outside of loops, it works like in Python2. Not really good news for python-style functional programming, I suppose.

% -- are you sure it works exactly like Python modulo? It seems to me Nim modulo differs when applied to negative numbers...

// -- thumbs up for alternative in result type (int | float).

print and printImpl -- I wondered if varargs[string, `$`] would not suffice but indeed it doesn't.

conversions -- I quite like them, very pythonic.

Also, you used BiggestFloat and BiggestInt in parsing but int and float in //... Additionally, Python's integers are actually bigints so I'm not sure if this choice won't lead to some nasty bugs or inconveniences...

Do you plan to support some equivalences of magical methods (that's apropos of bool converter)?

honhon (orginal) [2017-08-27T07:19:24+02:00] view original

That's neat! Well done.

Tiberium (orginal) [2017-08-27T11:44:24+02:00] view original

Udiknedormin: I've fixed modulo (If I'm not mistaken), added a couple of tests. About range - I plan to make it an object, so it would be lazy too (as in python 3).

Yeah, I can't write print as an simple procedure because Nim doesn't have keyword-only arguments

dom96 (orginal) [2017-08-27T13:56:01+02:00] view original

Thanks to you I noticed there are finally proper AST nodes for doc-comments

I'm fairly sure we had AST nodes for doc comments since forever.

I can't write print as an simple procedure because Nim doesn't have keyword-only arguments

Not quite, you can't write it because you cannot mix varargs and keyword-only arguments in Nim.

Tiberium (orginal) [2017-08-27T14:38:07+02:00] view original

Udiknedormin, I've added lazy evaluation for range - https://github.com/Yardanico/nimpylib/blob/master/src/pylib/range.nim

Udiknedormin (orginal) [2017-08-27T17:21:21+02:00] view original

Nice. :) May we move to github for further detailed discussion?

Tiberium (orginal) [2017-08-27T17:21:39+02:00] view original

Udiknedormin: yeah, or maybe IRC

Krux02 (orginal) [2017-08-28T03:42:50+02:00] view original

@dom96 I am fairly sure that I submitted a pull request (that got accepted) not that long age that fixed the doc comments.

Udiknedormin (orginal) [2017-08-28T19:59:40+02:00] view original

@dom96 I am quite sure that when I was writing some macros in Nim some time ago, it was clearly stated somewhere that doc-comments cannot be read from (or created as) AST.

Mirror of forum.nim-lang.org

3123 :: Simple Python-like class macro and some python-like procedures (print, input, range, others)