Feature request:
Add a command-line option to pass a first command to the interpreter.
For example:
$ apl --init ')LOAD foo'
Note the ways in which the example differs from $ apl -f foo.apl :
- the file is loaded from the workspace directory
- no foo.apl.log file is created
- the contents of f
$ apl -f nosuchfile
__ _ __ __ _____ __
/ // | / // / / / / | / __ \ / /
/ / __ / |/ // / / / / /| | / /_/ // /
/ /_/ // /| // /_/ / / ___ | /
On Mon, 2014-06-16 at 10:32 -0700, David B. Lamkins wrote:
> There does not seem to be a case in which fixing a function results in a
> timestamp other than 0 0 0 0 0 0 0 as a result of 2⎕AT. However, saving
> a workspace via )OUT does result in *some* functions having a reasonable
> timestamp whil
Hi Elias:
Sorry but I am totally ignorant about Android so don't know how the following
comments apply, if at all.
As a first step in OS X I am going to experiment with setting up file handles
for pipes, setting up NSNotifications, and launching a sub-task.
See NSTask documentation and sample c
The GNU license does not allow non-GNU-licensed code to be linked with the
binary. There is no question the Android port has to be GNU-licensed as
well.
Regards,
Elias
On 17 June 2014 04:28, Peter Teeson wrote:
> Hi Jürgen:
> Thanks for responding to my proposal.
> Yes I understand and didn't
Hi Jürgen:
Thanks for responding to my proposal.
Yes I understand and didn't take static into account.
I do like your cleaner and simple proposal.
Where would the source for all these Class XyzInput files be hosted?
Part of the distribution? Or would the end user supply them at build time?
I would
There does not seem to be a case in which fixing a function results in a
timestamp other than 0 0 0 0 0 0 0 as a result of 2⎕AT. However, saving
a workspace via )OUT does result in *some* functions having a reasonable
timestamp while others have their timestamp set to the Linux Epoch (1970
1 1 0 0
Understood.
Given that perspective, I'd argue that )OUT should not warn about saving
a native function. After all, what's being saved is only an expression
using an extension to quad-FX.
GNU APL should, of course, continue to support the )out -> )in
round-trip of a workspace containing features s
Note that the Android port doesn't really do input. It's all event-driven
from the user interface. That said, I'll need to deal with quad-assignment.
Trying that right now would cause it to hang since there is no way to send
input to stdin.
So yeah, I'd need some mechanism by which I can be inform
Hi Peter,
I see a few problems with your proposal.
Currently class *Input* has only static functions, so virtual methods
can not be used to distinguish
between different implementations of the same function.
Suppose we would fix that by using *Input* instances. Instead of eg.
#*ifdef HAVE_AN
Hi Fred,
thanks, fixed in SVN 330.
/// Jürgen
On 06/16/2014 03:48 AM, Frederick H. Pitts wrote:
Hello Juergen,
For sometime now, I've noticed that the first line of the )DUMP command
output is
#!/usr/local/bin//usr/local/bin --script --
Is this correct?
#!/usr/loca
Hi Elias,
thanks, included in SVN 329.
/// Jürgen
On 06/15/2014 10:06 PM, Elias Mårtenson wrote:
Do you think it would be possible to apply this patch that avoids
setting up the output streams when compiling for Android? The Android
version installs its own that redirects the output to Java
Hi Peter,
thanks, fixed in SVN 329.
I have also change the Makefiles a little to be more picky (-Wall)
/// Jürgen
On 06/15/2014 06:57 PM, Peter Teeson wrote:
GNUAPL/apl-svn/src/UTF8_string.cc:273:1: Control reaches end of non-void
function
Hi David,
it is generally impossible in APL to check if a function uses a feature
or not.
For example *A ⎕CR B* may or may not use dyadic *⎕CR* (which is a GNU
APL extension),
depending on whether *A* is a variable or a function.
And *)OUT *simply dumps the function's *⎕CR* without further
14 matches
Mail list logo
