OpenEuphoria

Thanks for expanding my understanding...

So far I see Python (a teaching language) has more programming traps than Euphoria.

The Python Division Trap is found in Python2.7; Python3 has fixed the problem by introducing the // operator for integer division (but is not in common use.)

The Python Octal Trap is nasty since we normally teach everyone that a zero before a number does not change its value.

I wish it didn't do that:

• puts crashes when some text is nested in a string
  • puts behaves as described, still a common error
• can't use = to compare strings or sequences
  • probably a common wish-list idea
  • needs more emphasis in the documentation
• self-modifying loops
  • expect them to work instead of crashing
  • better examples and explanations needed
• short-circuit evaluation
  • the different actions for conditionals and expressions is documented
  • but, my head hurts before I finish reading
• input and output in Euphoria is different from conventional language
  • need and automagic output routine
  • display is a bit of a monster
• no string data-type
  • novices sometimes complain, not understanding how Euphoria works

Documentation at fault? It it crashes it is not a "trap."

In a "for structure" the start and finish limits are locked-in at the time of writing; changing a for loop into an infinite loop while running is a bad idea. ( The "Python for structure" doesn't work any better. It also looks Python designers even created immutable data-types to prevent self-modifying code. )

The descriptions and examples for looping structures need a make-over.

TOM