@NathanH13

Baseline functionality is generally based on AmigaOS 3.1.

Yes, bug reports would be extremely welcome, no matter how minor. Ideally individually reported in the Sourceforge bug tracker.

Thanks!

I've attached the fixed List command.

Attach file:

---

Link only for registered users

Quote:
i totally missed that part . you are right .
In that case, setenv does the same behaviour.

red:
come to think about it. Isn't it so that readitem 'just' splits up arguments when space _or_ '=' is encountered (exception quoted) ? that would explain the behaviour. It then fails only when the parameters are exactly as named (or another priority is given to recognizing the named arguments)

Quote:

Yes, but in this case you are combining two separate parameters with the '='. If it works in AmigaOS, I suspect it is a hack built into its Set command.

Quote:
in case of both classic and aros:
NAME,STRING/F

But afaic remember it is/was always possible in classic to use the OPTION=VALUE pair in/for every parameter of a shellcommand. It was just preferences made by user.

Lightbulb going of!?

I've been trying to get a bunch of my Amiga OS scripts running under icAROS. To me, its amazing how well things work but its also frustrating because of the many _extremely minor_ oddities I run across; even amongst different versions of Amiga OS.

Is there one particular OS 3.0 CD that is the definitive standard of C: and RexxMast versions that is being captured in AROS? Or perhaps a list of all versions of C: to be targeted. If that was known, my UAEPipe and SQL scripts could provide an automated and searchable test suite of functionality using examples from (what I use as my bible) Mastering AmigaDOS.

Would this be useful or duplicative to work elsewhere? Report deviations one-at-a-time or in one fell swoop? Thanks.

Nathan

@magorium

Thanks for the research.

What does "Set ?" show?

@NathanH13

I think your book's differentiation between creation and modification dates is bogus, because native Amiga filesystems do not store a creation date/time.

Hi Neil,

I can confirm the behaviour as decribed earlier.

Although my reference stated that the format can be manipulated by the dateformat variabele, i myself could not manipulate it with classic OS (workbench 40.42).

So the only thing left that afaik could influence this is the selected country (haven't tried that).

I think it's save to say your patch is valid, as it showed exactly the same behaviour for me in classic.

Sorry for any confusion i might have caused.

regards


PS: dunno if it is/was adressed already, but i also noticed i can use "set myvariable=myvalue" using classic, which failed for me under Icaros.

Thanks folks. Sorry about that, from Mastering AmigaDOS pg.165:

"By default, LIST always tries to specify the weekday and time of a file's creation (assuming the file was created recently). This switch tells it to display the exact date the file was last MODIFIED [caps from original text]."

Simple example for anyone running icAROS and Amibridge OS3.0:
From icAROS Shell:
Ram:
List
Clipboards <Dir> ---rwed Today 18:54:37
ENV <Dir> ---rwed Today 18:54:41
T <Dir> ---rwed Today 19:11:23
3 directories - 3 blocks used

List DATES
Clipboards <Dir> ---rwed Today 18:54:37
ENV <Dir> ---rwed Today 18:54:41
T <Dir> ---rwed Today 19:11:23
3 directories - 3 blocks used

From OS3 Shell:
Ram:
List
Disk.info 2556 ----rwed Today 19:13:55
ENV Dir ----rwed Today 19:13:54
Clipboards Dir ----rwed Today 19:13:52
T Dir ----rwed Today 19:14:14
1 file - 3 directories - 10 blocks used

List DATES
Disk.info 2556 ----rwed 25-Jan-13 19:13:55
ENV Dir ----rwed 25-Jan-13 19:13:54
Clipboards Dir ----rwed 25-Jan-13 19:13:52
T Dir ----rwed 25-Jan-13 19:15:05
1 file - 3 directories - 10 blocks used

Thanks,

Nathan