Author: Compynerd255
Posted: 12 Oct 2012 01:05:21 pm (GMT -5)
Nice changelist. I like the first syntax under number 10 better, because the data for a cofunc feels less like metadata (what would go in a header) and more like an asset the cofunc possesses. The name should definitely go before the data.
Out of curiosity, are there any plans for an Antelope IDE, either as a standalone program or as an extension of an already existing IDE? I'd love to be able to step and trace an Antelope program.
In fact, I have this old Apple //e connected to my computer via a serial port, and I think it would be an awesome project to write an implementation of Antelope for the Apple, complete with a system that deploys the program to the Apple (over the serial line) and uses an Apple-side program to interact with the remote debugger.
_________________
Visit Betafreak Games: http://www.betafreak.com
Help Me Pay for College:
- Sign up for Fastweb through my referal link!
Posted: 12 Oct 2012 01:05:21 pm (GMT -5)
Nice changelist. I like the first syntax under number 10 better, because the data for a cofunc feels less like metadata (what would go in a header) and more like an asset the cofunc possesses. The name should definitely go before the data.
Out of curiosity, are there any plans for an Antelope IDE, either as a standalone program or as an extension of an already existing IDE? I'd love to be able to step and trace an Antelope program.
In fact, I have this old Apple //e connected to my computer via a serial port, and I think it would be an awesome project to write an implementation of Antelope for the Apple, complete with a system that deploys the program to the Apple (over the serial line) and uses an Apple-side program to interact with the remote debugger.
_________________
Visit Betafreak Games: http://www.betafreak.com
Help Me Pay for College:
- Sign up for Fastweb through my referal link!