On Tue, 25 Sep 2012 16:23:19 +0200, Michael Haberler wrote:
> Am 25.09.2012 um 16:12 schrieb EBo:
>
>> Assuming that you are talking about a PATH list (similar to how most
>> *NIX shells deal with ${PATH}) then I would suggest not setting the
>> current directory as the default first choice. Sometimes you want
>> to
>> explicitly overload something and you need to make sure that you can
>> put
>> it before the system one. Also, assuming "." or current directory,
>> have
>> been used in the past to inject trojans and viruses on *NIX
>> machines. I
>> think we should think twice about allowing that if a rogue
>> subroutine
>> could be injected...
>
> then redefine SUBROUTINE_PATH to allow a '.', or '$dir', or whatever
> you like which gets substituted at runtime by dirname(gcodefile)
my understanding is that that functionality was not working. I agree
that it would be useful to have SUBROUTINE_PATH be defined to something
like ". /usr/share/linuxcnc/examples /some/other/place"
EBo --
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
