systemml-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Boehm (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYSTEMML-2232) Logical namespace handling user-defined functions
Date Wed, 04 Apr 2018 23:59:00 GMT

    [ https://issues.apache.org/jira/browse/SYSTEMML-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426349#comment-16426349
] 

Matthias Boehm commented on SYSTEMML-2232:
------------------------------------------

Well, this would likely create problems regarding recursive namespace resolution, so I would
recommend to keep both the filename and the logical namespace. This way the current runtime
remains unchanged but we can use the logical name spaces where needed (e.g., for better stats
output and namespace functions in eval).

However, not that I recommend this task for a potential new contributor, so it would be polite
to leave this task open for a while: https://www.mail-archive.com/dev@systemml.apache.org/msg00630.html.

> Logical namespace handling user-defined functions
> -------------------------------------------------
>
>                 Key: SYSTEMML-2232
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-2232
>             Project: SystemML
>          Issue Type: Task
>            Reporter: Matthias Boehm
>            Priority: Major
>
> At script level functions might have logical namespace names such as {{foo::bar()}},
where foo is the namespace name, and bar is the function name. To handle namespace conflicts,
SYSTEMML-631 internally replaced the logical namespaces with filenames. For reasons such as
improved statistics output and the handling of namespace functions in the recently introduced
{{eval}} function (SYSTEMML-2077), it would be good to keep the logical namespace as well.
> This task aims to (1) extend the {{FunctionStatementBlock}} and {{FunctionProgramBlock}}
data structures to keep the logical namespace name, (2) extend the parser and compiler accordingly,
and (3) modify the statistics maintenance to use the function key (i.e., concatenation of
logical namespace and function name) as the opcode.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message