Re: [Factor-talk] Variable command-line only contains arguments
Am Tue, 23 Dec 2014 11:22:49 -0800 schrieb John Benediktsson mrj...@gmail.com: Hi John, USE: command-line executable get command-line get works. Thank you. for now I cannot make deploy work in the new the nightly build. I started a new thread: deploy no longer working with new nightly build Georg Hi Georg, The nightly builds are updated now if you want to try them (Win64 is not yet ready because of some updates that @erg is currently doing on the Win64 build server). I made it so that, similar to Python, you can get the executable separate from the command-line arguments. USE: command-line executable get command-line get The executable will usually be the Factor binary, but in a deployed application will be the deployed binary. I also updated the docs a little bit to make this more clear. Let me know if this works for you! Best, John. signature.asc Description: PGP signature -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Variable command-line only contains arguments
Am Mon, 22 Dec 2014 22:45:55 -0800 schrieb John Benediktsson mrj...@gmail.com: Hi John, thank you. So I can wait for the next nightly build I assume. Georg Hi Georg, I pushed a fix to provide you the executable name. Basically the ``(command-line)`` word in the command-line vocabulary is the raw command-line, which includes all command-line arguments including the executable. The ``command-line`` symbol is where we keep the other arguments to the script. If you need the executable name, you can just call ``(command-line) first`` for right now. (Assuming you update to master) Best, John. On Mon, Dec 22, 2014 at 9:32 AM, John Benediktsson mrj...@gmail.com wrote: We try and make it consistent between deployed and non-deployed applications. It looks like we are not storing the executable name right now (argv[0]). Probably we should fix that I guess! If we fix it in master are you comfortable running a nightly build? (They are well tested before the build successfully uploads) On Dec 22, 2014, at 9:24 AM, Georg Simon georg.si...@auge.de wrote: Am Mon, 22 Dec 2014 06:51:22 -0800 schrieb John Benediktsson mrj...@gmail.com: Hi Georg, I don't see a difference between deploy and when a script/vocabulary is run directly. Is your question about deploy, or how to obtain the command/executable name? Thanks, John. Hi John, yes I wanted to obtain the executable name in a deployed application. But my main point is that for me the documentation is misleading. The documentation made me think that I could find the executable name in the variable command-line. Georg -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk signature.asc Description: PGP signature -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Variable command-line only contains arguments
Hi Georg, The nightly builds are updated now if you want to try them (Win64 is not yet ready because of some updates that @erg is currently doing on the Win64 build server). I made it so that, similar to Python, you can get the executable separate from the command-line arguments. USE: command-line executable get command-line get The executable will usually be the Factor binary, but in a deployed application will be the deployed binary. I also updated the docs a little bit to make this more clear. Let me know if this works for you! Best, John. On Dec 23, 2014, at 1:59 AM, Georg Simon georg.si...@auge.de wrote: Am Mon, 22 Dec 2014 22:45:55 -0800 schrieb John Benediktsson mrj...@gmail.com: Hi John, thank you. So I can wait for the next nightly build I assume. Georg Hi Georg, I pushed a fix to provide you the executable name. Basically the ``(command-line)`` word in the command-line vocabulary is the raw command-line, which includes all command-line arguments including the executable. The ``command-line`` symbol is where we keep the other arguments to the script. If you need the executable name, you can just call ``(command-line) first`` for right now. (Assuming you update to master) Best, John. On Mon, Dec 22, 2014 at 9:32 AM, John Benediktsson mrj...@gmail.com wrote: We try and make it consistent between deployed and non-deployed applications. It looks like we are not storing the executable name right now (argv[0]). Probably we should fix that I guess! If we fix it in master are you comfortable running a nightly build? (They are well tested before the build successfully uploads) On Dec 22, 2014, at 9:24 AM, Georg Simon georg.si...@auge.de wrote: Am Mon, 22 Dec 2014 06:51:22 -0800 schrieb John Benediktsson mrj...@gmail.com: Hi Georg, I don't see a difference between deploy and when a script/vocabulary is run directly. Is your question about deploy, or how to obtain the command/executable name? Thanks, John. Hi John, yes I wanted to obtain the executable name in a deployed application. But my main point is that for me the documentation is misleading. The documentation made me think that I could find the executable name in the variable command-line. Georg -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
[Factor-talk] Variable command-line only contains arguments
http://docs.factorcode.org/content/word-command-line,command-line.html says: In deployed applications, it contains the entire command line. But in my deployed application I only get the arguments and not the command name. Georg signature.asc Description: PGP signature -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Variable command-line only contains arguments
Hi Georg, I don't see a difference between deploy and when a script/vocabulary is run directly. Is your question about deploy, or how to obtain the command/executable name? Thanks, John. On Mon, Dec 22, 2014 at 2:21 AM, Georg Simon georg.si...@auge.de wrote: http://docs.factorcode.org/content/word-command-line,command-line.html says: In deployed applications, it contains the entire command line. But in my deployed application I only get the arguments and not the command name. Georg -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Variable command-line only contains arguments
Am Mon, 22 Dec 2014 06:51:22 -0800 schrieb John Benediktsson mrj...@gmail.com: Hi Georg, I don't see a difference between deploy and when a script/vocabulary is run directly. Is your question about deploy, or how to obtain the command/executable name? Thanks, John. Hi John, yes I wanted to obtain the executable name in a deployed application. But my main point is that for me the documentation is misleading. The documentation made me think that I could find the executable name in the variable command-line. Georg signature.asc Description: PGP signature -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Variable command-line only contains arguments
We try and make it consistent between deployed and non-deployed applications. It looks like we are not storing the executable name right now (argv[0]). Probably we should fix that I guess! If we fix it in master are you comfortable running a nightly build? (They are well tested before the build successfully uploads) On Dec 22, 2014, at 9:24 AM, Georg Simon georg.si...@auge.de wrote: Am Mon, 22 Dec 2014 06:51:22 -0800 schrieb John Benediktsson mrj...@gmail.com: Hi Georg, I don't see a difference between deploy and when a script/vocabulary is run directly. Is your question about deploy, or how to obtain the command/executable name? Thanks, John. Hi John, yes I wanted to obtain the executable name in a deployed application. But my main point is that for me the documentation is misleading. The documentation made me think that I could find the executable name in the variable command-line. Georg -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] Variable command-line only contains arguments
Hi Georg, I pushed a fix to provide you the executable name. Basically the ``(command-line)`` word in the command-line vocabulary is the raw command-line, which includes all command-line arguments including the executable. The ``command-line`` symbol is where we keep the other arguments to the script. If you need the executable name, you can just call ``(command-line) first`` for right now. (Assuming you update to master) Best, John. On Mon, Dec 22, 2014 at 9:32 AM, John Benediktsson mrj...@gmail.com wrote: We try and make it consistent between deployed and non-deployed applications. It looks like we are not storing the executable name right now (argv[0]). Probably we should fix that I guess! If we fix it in master are you comfortable running a nightly build? (They are well tested before the build successfully uploads) On Dec 22, 2014, at 9:24 AM, Georg Simon georg.si...@auge.de wrote: Am Mon, 22 Dec 2014 06:51:22 -0800 schrieb John Benediktsson mrj...@gmail.com: Hi Georg, I don't see a difference between deploy and when a script/vocabulary is run directly. Is your question about deploy, or how to obtain the command/executable name? Thanks, John. Hi John, yes I wanted to obtain the executable name in a deployed application. But my main point is that for me the documentation is misleading. The documentation made me think that I could find the executable name in the variable command-line. Georg -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
