This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - NecroBumpist
Pages: 1 ... 5 6 [7] 8 9 10
91
« on: August 27, 2011, 05:54:04 pm »
The Night Angel Trilogy by Brent Weeks is absolutely godly.
The Black Prism by the same author was also great.
The Pendragon series was very good. Very looooonnngg, but I enjoyed it.
Finally, the Innocent Mage series by Karen Miller was great as well.
92
« on: August 22, 2011, 10:20:43 pm »
I love brainf*ck! I also love ><> 
93
« on: August 22, 2011, 06:56:42 pm »
pianoman, I'm dearly sorry. I really have been neglecting properly documenting everything. I'll get working on that after I answer your questions  Which file/folder would we make the example script you showed above in?
Then, once we do that, which script do we run to convert to bytecode?
You could run it in the \src\ folder I believe. The script you would use to convert it is the "current.lua" one. So you would first have to require() that, (sort of like #include) -- let's assume this script is in the \src\ folder
local mods = require("current"); -- this runs current.lua, which returns a table of the major API functions
local bytecode = mods.Assemble([[
; put cool bytecode here
]]); -- this passes the multi-line string argument to Assemble(), which turns it into bytecode
-- The easiest way to utilize bytecode in a script is in an escape sequence like so: \104\101\108\108\111 (this is the ASCII sequence "hello")
print(bytecode:gsub(".", function(a) return "\\" .. a:byte() end)) -- this is the bytecode in the above format, which you can pass as a string argument to loadstring()
And, finally, how do we run Lua scripts like that on the computer?
You would need the Lua executables: - For Linux: Download the source code and compile or find the proper package to install
- For Windows: Download LuaForWindows
Any chance you could make some sort of an API/less confusing and nspire-oriented tutorial?
Yes I will also add command line support so you can do the following: >lua current.lua input.lasm -o output.lua
Which will create a .lua file that will loadstring() an ASCII sequence like I demonstrated above Also, thanks ExtendeD 
94
« on: August 21, 2011, 07:57:42 pm »
1938: You apparently cannot properly read the site banners, but will come back tomorrow compulsively anyway.
95
« on: August 21, 2011, 06:25:41 pm »
#1936: You anxiously await your 40th post so you can join the IRC channel
96
« on: August 21, 2011, 05:42:43 pm »
I don't go to any concerts this summer. Speeking of concerts, I found this today: Welcome to the future, Where the music business is dominated by robotic sounding vocals, and almost holographic band members.
97
« on: August 21, 2011, 04:05:45 pm »
How was your trip ?
98
« on: August 21, 2011, 02:40:41 pm »
Bricks were bigger for young children so they avoid swallowing them.
Wouldn't the bricks have to get systematically bigger so that they're harder to fit into the bigger mouths of older children ?
99
« on: August 21, 2011, 02:33:34 pm »
 Just another way that the older you get, the less fun you can have.
100
« on: August 21, 2011, 12:51:13 pm »
NOTE: I did not make this, but since the NSpire does not have gigabytes of memory, I though I would share it with you guysLuaSrcDietI found this project a while back (It's made by the author of ANoFrillsIntroToLua51VMInstructions.pdf), and I think it could be of use for NSpire Lua developers. Basically, what it does is it removes as much unnecessary information as possible. This means removing whitespace, comments, and renaming/reusing variables whenever possible. I just used it again on a script of mine that was 38,513 bytes long. It outputted a file 21,899 bytes long. That's a 41% reductionEverything should run the same. (Though if you have an error it might be harder to figure out which variable it was really from) So if you're looking to save space in large projects of yours, you might want to give this a try
101
« on: August 21, 2011, 11:56:46 am »
Yes, that wouldn't run, TI removed file interactions. The examples are really meant to be ran on a desktop. I would not advocate using this on your calculator (as I've said before, it's slow), but I'll steal ocLua's concept so you can, just for fun Edit: in the \bin\ directory there is now a "ocLASM.tns" file. It works exactly like ocLua (many many thanks to ExtendeD ) Though I still don't recommend actually typing LASM on an NSpire, as it is really tedious.
102
« on: August 21, 2011, 11:06:59 am »
There's a math.eval() function for interacting with TI-Basic, so you might be able to call a pre-existing function from that.
/speculations.
103
« on: August 21, 2011, 10:49:35 am »
Everybody knows that they want their older product lines die as soon as possible... but they didn't _have_ to wrongfully indicate that the 89T does not do 3D graphing, that the TI-68k and TI-Z80 series does not contain preloaded applications, or that the 89T cannot do split screen (not up to 4-way, but 2-way - so they ought to have made this line contain numeric values, if they were honest)...
>big corporations
>honestNope 
104
« on: August 21, 2011, 10:41:59 am »
Really nice indeed.
Looking forward to be able to test that project in more complex situations, once I understand how to program in this asm-looking language
Thanks I definetely do more basic documentation on the features of the assembler. After that, I've included a copy of ANoFrillsIntroToLua51VMInstructions.pdf in the \docs\ folder(the de facto document for learning Lua bytecode, and ultimately Lua assembly) So that should be a great reference to all those who want to learn the specifics of a particular instruction. I'll get to work on explaining how to use everything now
105
« on: August 21, 2011, 12:52:19 am »
(note that yellowish text is fake for the newbies)
(This )
Damnit! Anyway, how long has that page really been like this ?
Pages: 1 ... 5 6 [7] 8 9 10
|
Show Posts