d the remaining
test programms
Target Phase:
- Copy that directory to the target
- Run the configuration phase and get the Config file
The challange would be to get the miniparrot running on the target.
All the rest should be covered by the "normal" Parrot Configuration Probing.
This is abo
Gregory Keeney wrote:
Thomas Seiler wrote:
Couldn't we split the probing into two phases ?
The problem is that getting stuff on and off your target host is not
always trivial. [...]
It is especially not true in the embedded world. Until I have parrot IO
libraries, I am not going to be ge
a string in the language
is was originally written, to access it from other languages, we should
use an interface that allows us to index it via just that string.
All the other logic needed to import stuff should be left to a module
for that given language. It knows better wich types have to be converted
which functions need wrappers, etc ...
just had to give my 2 cents on namespaces :)
Thomas Seiler
Dan Sugalski wrote:
At 10:34 AM +0100 11/27/04, Leopold Toetsch wrote:
See also subject "Too many opcodes".
>> [...]
>>
Could you undo this please? Now is not the time to be trimming ops out.
OTOH, it won't hurt anyone and it is already in.
So why bother, unless of course there is a technical reaso
Leopold Toetsch wrote:
Thomas Seiler <[EMAIL PROTECTED]> wrote:
Dan Sugalski wrote:
At 10:34 AM +0100 11/27/04, Leopold Toetsch wrote:
See also subject "Too many opcodes".
[...]
Then there are changes that need more thought:
* replacing *_i_n with *_n_n uses a N-register and mig
Leopold Toetsch wrote:
[...]
Just if you had 32 N regs used before. It's using only one additional
register.
[...]
I did not touch any PMC ops.
You are of course right, maybe I hadn't had enough coffee this morning.
Sorry for the bother, and keep up the good work.
tom (who is going back into shy-
At Tue 30 Nov 6:22pm, Dan Sugalski wrote:
> Architecture changes aren't an option we're entertaining until after we're
> functionally complete.
Just would like to ask a related question:
Is a change that invalidates an existing precompiled bytecode but not
the source code of it
considered as an ar
I have the impression that there has been some confusion about the term
"opcode"
There are IHMO two things that qualify for beeing an "opcode":
* Mnemonics: These are Strings that help humans to write in assembly,
i.e. ' ADD' in PASM.
* Instructions: These are words of bits that are executed by
