Python Forum
parse tree vs just tokenizing
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
parse tree vs just tokenizing
#4
i originally thought of tokenizing in a different way, more like what command would need. i wrote some code to do that back in my C days and also way back in my assembler days. so i was thinking in those terms. i haven't needed anything like that, yet, so i had no reason to look at the tokenize module. i knew it existed but hadn't had a reason to read up on it.

well, now i have, and not only is it a solution to my immediate need, but it looks like something i can do many things with, including a Python oriented editor where i can have string substitution be applied to specific language parts. for example, change "foo" to "bar" in names, not in string literals.

i'm playing around, tonight.
Tradition is peer pressure from dead people

What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
Reply


Messages In This Thread
parse tree vs just tokenizing - by Skaperen - Jul-01-2021, 11:54 PM
RE: parse tree vs just tokenizing - by Gribouillis - Jul-02-2021, 06:12 AM
RE: parse tree vs just tokenizing - by Skaperen - Jul-03-2021, 10:53 PM
RE: parse tree vs just tokenizing - by Skaperen - Jul-04-2021, 04:05 AM
RE: parse tree vs just tokenizing - by Skaperen - Jul-04-2021, 07:41 PM
RE: parse tree vs just tokenizing - by Gribouillis - Jul-04-2021, 08:53 PM

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020