No-op statements syntactically valid only since Python X.Y

Re:No-op statements syntactically valid only since Python X.Y by eesmith on Monday June 06, 2022 @02:54PM (#31644263)

I realize now how much of a hack it is. The portion 'm/(ATOM |HETATM)/' could be part of valid Python expression, as:

  >>> ATOM = HETATM = 1
  >>> m = 2
  >>> m/(ATOM  |HETATM)/1
  2.0

so either m// is enabled only after =~, or there has to be some way to recognize the lexically correct match term -- something more powerful than the "m/[^/]*/[a-z]*" used here.

[ Parent | on HN ]

There are no comments on this comment yet.