Jump to content
UNIXcoffee928

Datasoft INTER-LISP/65

Recommended Posts

I just read somewhere in documentation about doubled semicolumns ...

Where please? As I am on the last fixes in the user guide for the coming V. 4.48 I'd like to know.

 

And if you need some special subdirectories you may set it up during boot.

But this implies you have read and understood how it works.

Share this post


Link to post
Share on other sites

I only want to say that SDX doesn't behave in the same convenient way as DR-DOS, PD-DOS, MS-DOS while reading PATH.

This is a question of convenience, SDX surely resembles MS-DOS and friends, but sometimes differs a bit, because it is not MS-DOS, it is SDX :)

 

Maybe it would help if you said what were you trying to accomplish. E.g. if you want to put the current directory before CAR:, then do:

 

SET PATH=:;CAR:

Share this post


Link to post
Share on other sites

Hi Friends!

 

I never tried to CRASH any status of SDX

It's VERY HARD!

 

BUT I saw some programs behavior, when some of programs which are being
called from another programs LOST their paths replacing it with simplest D1:..

 

You always know that I can NOT show you my evidences.

 

Hi Drac030!

I'll try your way...

 

Hi GBXL... I read this matter more then week ago... I'll try to give you links...

Share this post


Link to post
Share on other sites

BUT I saw some programs behavior, when some of programs which are being

called from another programs LOST their paths replacing it with simplest D1:..

Yes, this is the presetting of the programmer and SDX cannot fix it. E.g. BASIC XE does it when calling DIR. Use "DIR D:*.*" instead and it calls the current directory on the current drive.

 

I read this matter more then week ago... I'll try to give you links...

It would be nice if you could provide hard facts as it is strange to me.

As Draco mentioned, when booting you may setup whatever directory structure you like to use for programming. And using the SDX Imager allows you to change the default config.sys. All described in the user guide. Maybe this is not understandable to everyone reading the user guide as it is unique in the A8 world.

Share this post


Link to post
Share on other sites

This is a CITE in SDX 4.47 manual:

 

For example OPEN #1,4+32,0,"D:CONFIG.DAT" will search the path defined by the
environment variable $PATH for the file. This will not work when opening a file for write
or update, since this could cause unexpected and possibly dangerous things to happen.
Because of these changes, it is a good idea to make the current directory the second
entry in the path. Changing the above example to do this would produce 'PATH
CAR:;;A:\DOS\;A:\TOOLKIT\;D9:>;A:>;:>' where the two semicolons after 'CAR:' signify
that current directory should be searched.

 

May be last phrase confused me? :-o

YES! I know that there are a lot of Atari programs with internally hardcoded path ...

Share this post


Link to post
Share on other sites

This is a CITE in SDX 4.47 manual:

 

For example OPEN #1,4+32,0,"D:CONFIG.DAT" will search the path defined by the

environment variable $PATH for the file. This will not work when opening a file for write

or update, since this could cause unexpected and possibly dangerous things to happen.

Because of these changes, it is a good idea to make the current directory the second

entry in the path. Changing the above example to do this would produce 'PATH

CAR:;;A:\DOS\;A:\TOOLKIT\;D9:>;A:>;:>' where the two semicolons after 'CAR:' signify

that current directory should be searched.

 

May be last phrase confused me? icon_surprised.gif

YES! I know that there are a lot of Atari programs with internally hardcoded path ...

 

Thank you for your help.

 

It is the section about the SEARCH PATH which is READ ONLY, as stated in that section.

 

We'll look into to see if it can be made easier to read and understand.

Share this post


Link to post
Share on other sites

I see and highly appreciate your work! :thumbsup:

 

I just search someway common Sparta(disk)-SDX environment for using it in programming.

 

As far as it's concerned LISP it's not a problem at all.

LISP knows nothing about search PATH (moreover it knows nothing about DIR! It's DIR command is a little joke I think.)

and absolutely workable in its own directory FE C:\LISP.

 

In other cases there are obvious problems.

FE for PL65 I slightly edited it's TEXT libraries to replace D1: to D: and work done.

 

But some C-linkers have hardcoded D1: path and cant be used in common way.

All problems begins when I want to use C:\ hard drive or H:\ Ramdisk FE.

 

EZ

Share this post


Link to post
Share on other sites

This cannot be done with $PATH, as most programs do not open files with $PATH searching: this mode has to be deliberately enabled when the application is doing an OPEN call, as in the example you have quoted above:

OPEN #1,4,0,"D:FOO.BAR" - open FOO.BAR located in current directory of the current drive

OPEN #1,4,0,"D1:FOO.BAR" - open FOO.BAR located in current directory of the specified drive

OPEN #1,4+32,0,"D:FOO.BAR" - search through $PATH for the FOO.BAR (this also includes the current drive/dir)

For programs which contain hardcoded references to D1: you can use the SWAP command to redirect (all, globally) the D1: references to another drive.

Edited by drac030

Share this post


Link to post
Share on other sites

I even never heard about swap...

 

Absolute command - READ MANUALS! :)

 

But you know that there are 3 or more peoples that writes tones of mans and someone reading is the only one!

 

I must say that SDX manuals are VERY comfortable!

 

thus I'll be in reading... ;)

 

Showing of the way is the role of teachers!

 

EZ

Share this post


Link to post
Share on other sites
Workaround to eliminate some quirks of InterLISP/65 in SDX.


At first, I must say that InterLISP/65 has an unqtue ability on atari-8 !!!

It's a pretty-printing !

No other lang has it! (IMHO)


BUT!

What we can do with 40 columns limit while LISP has no limit in it's logic line at all?!! (Only a RAM limitations.)


So, we need 80 columns!

- And it's a beginning of my investigations...


Good old Konrad (Drak030), said me a secret word to familiarize LISP with SDX. :)

POKE 02e4,$c0. And it works in COL 40 mode!


Also, never working with LISP he has never meet it's real problems.


Recently I've tried to run LISP in SDX in COL 80 and COL 64 (I prefere COL 64) environment with the purpose to get a real pretty-printing of some long-enough LISP program such as LISP's 'EDIT - structured-manner LISP-native EDITOR.


No chance.

May be 'Screen' or '80font' are destroyed while loading LISP, may be some other garbage come in to screen ...

I report this screenshot:

/Garbage

post-20208-0-49541100-1557125615_thumb.png

Thus we have some data/drivers in operative area while working.

So I decided to say 'Y' but 'N' while loading LISP 2.5 after the prompt:

Reserve mem for graphic modes 6,7,8

And a screenshot:

/Loaded

post-20208-0-73638100-1557125631_thumb.png

And it's pretty-printing screenshot.

/Success

post-20208-0-84391900-1557125652_thumb.png

P.S. I really can not understand which part of SDX is under the siege.

May be some relocation of standard SDX parts is a Panacea?

All your suggestions about relocation of SDX data are very highly appreciated.


Best wishes from Moscow

zen


Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...