Shell() return STDOUT

Page: 1 2
ID:1604013
 
Jun 18 2014, 5:44 pm
Applies to:DM Language
Status: Open
Issue hasn't been assigned a status value.
Currently shell() doesn't return STDOUT it for some reason only returns 0

My request is that shell() returns STDOUT, instead of having us write and read files over and over which causes unnecessary I/O on the disk.
Jun 19 2014, 8:13 am
^ Second.
Jun 19 2014, 9:26 am
For sure. ^
Jun 19 2014, 9:30 am
Agreed, but in the meantime you can write a fairly compact DLL/SO file that does this, I did it myself a while back.
Jun 19 2014, 1:36 pm
In response to Nadrew
Nadrew wrote:
Agreed, but in the meantime you can write a fairly compact DLL/SO file that does this, I did it myself a while back.

Are you able to supply the DLL/SO ?

Thanks.
Jun 19 2014, 1:46 pm
^ @A.T.H.K it's quite a small task so if Nadrew can't supply it, I'll create one for you
Jun 19 2014, 1:48 pm
Not to go too off topic, but what are the requirements on DLLs being called by call()?

I thought I heard you needed to use C or something. Is there anything I should know before attempting one? If anything I'd just google how to create a DLL and go from there. Sadly I'm mostly experienced in c# and suck in c/c++
Jun 19 2014, 1:57 pm
You create a C++ project for a .dll and use extern "C" __declspec and such.

This will allow BYOND to call the function/the .dll to export the function.

The example in the guide was a poor one, but it's an example nonetheless.
Jun 19 2014, 1:58 pm
In response to Ssj4justdale
Ssj4justdale wrote:
You create a C++ project for a .dll and use extern "C" __declspec and such.
This will allow BYOND to call the function/the .dll to export the function.
The example in the guide was a poor one, but it's an example nonetheless.

I mean, I can take what's in the guide and use it. I just don't understand what it's doing.
Jun 19 2014, 2:03 pm
That example just merges strings together.

The strcat function copies the source and appends it to the desination.

strcat(buf,v[i]) //taken from the guide

//buf is the desination/ the text we want to return / the final product

// v[i] is something inside the list/array that we want to append to "buf"
Jun 19 2014, 2:08 pm
Also, extern "C" means that you can use C in C++ because you are "linking" the two.
Jun 19 2014, 2:31 pm
Ah, thanks for that information. I'll refer to this thread when making my own. :)
Jun 19 2014, 2:39 pm
No problem, I'll be looking forward to seeing what you come up with :D
Jun 19 2014, 4:50 pm
Want me to share my .dll for it with you A.T.H.K? I just ran tests and it's also 3x faster than BYOND's built in shell() command. That's without BYOND getting a return value as well.
Jun 19 2014, 4:50 pm
I would make a .so but I never made one before haha.
Jun 19 2014, 4:54 pm (Edited on Jun 19 2014, 7:02 pm)
If you do, it could be found here: http://www.ssj4justdale.byethost13.com/res/shell_output.dll

http://www.ssj4justdale.byethost13.com/res/Snippet_src.zip

How to use it:

mob/verb/Test(T as text)
    src<<_shell("[T]")

proc/_shell(command_args)
    return call("shell_output.dll","shell")(command_args)


Jun 19 2014, 6:22 pm
You shouldn't be linking to stray dll files like that, virus scanners hate that a lot -- you should package it up with the source and the dll into a zip or something so people aren't just downloading a random dll file without context =P
Jun 19 2014, 6:42 pm
^ Noted. Will do so now.
Jun 19 2014, 7:01 pm
Jun 19 2014, 7:31 pm
Just curious are you able to do in the language BYOND uses and post the source? That way the developers could also use it with next to effort implementing it ;)

But awesome job nonetheless!!
Page: 1 2