Jump to content
  • Advertisement
  • entries
  • comments
  • views

More Epoch overload!

Sign in to follow this  


It always amazes me what I'm capable of debugging in my sleep. For instance, I had a nasty problem with infix operators in the Epoch parser that I just couldn't sort out last night; grab a few hours of shuteye, and bam, I woke up knowing exactly what to do about it. Got to love being productive and lazy at the same time!

So now infix operators work, sort of; there's still no precedence rule support in the new parser, which will be a righteous pain in the backside to reimplement. Instead of tackling that straight away, I've decided to go back to fundamentals and figure out why functions are no longer capable of returning anything. (In case you hadn't guessed, in a language that aspires to support pure functional programming as richly as possible, return values are kinda important.)

In the process I decided to sacrifice one of the oldest sacred cows in the Epoch toolbox, which is multiple return values. Epoch's first incarnation allowed functions to return multiple values via a tuple mechanism; unfortunately, tuples and structures became extremely similar, to the point where the distinction between them was largely academic and historical and not really practical at all. Since pragmatism is the guiding rule of the Epoch project, I figured it makes the most sense to axe tuples and collapse everything of that nature into structures.

Which brings us back to multiple return values: there's no point in having them anymore, if one can just return a structure instead. I may end up implementing some syntactic sugar support for anonymous return structures if it ends up being useful (God knows I love Lua's multiple-return system... well, sometimes). It shouldn't be too hard to add sugar to the new parser structure, because the goal of the new parser is basically to make everything syntactic sugar.

Anyways... I could ramble for a bit on how the new architecture will basically turn Epoch into a programming language generator rather than a strict language itself, but I should probably organize those thoughts a bit more before splattering them all over the page. So more on that later.

For now, back to making functions useful again!
Sign in to follow this  


Recommended Comments

I find its always the most bizarre bugs that sleep solves. I don't pretend to understand how it works, but my unconscious mind is clearly superior to my regular one...

Share this comment

Link to comment
You're lucky. I tend to solve my bugs just before completely falling asleep. Which wakes me back up, and leaves me trying to decide whether I should get up to implement the solution.

Share this comment

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!