XAS (Re: Tasm 4.0 to ASCII)

TEV> one whole track!!! this is very, very bad!!! if next versions
TEV> STORM will make support for upper memory, then I’ll go for it (maybe it’s
TEV> anyway, but many can do it) so I need
TEV> to think....

I also liked STORM. He would like the ALASM interface, and the rest is all perfectly
done.

Regards, Alex from FFC COMPUTERS.

>e-mail: as...@usa.net

Once I was in a museum and there on an old, old stone an ancient man carved that
Thursday March 26, 1998 right at 08:44, Alex Letaev wrote Tyukaev Eugene
Vladimirovich:

TEV>> what to think....

AL> I also liked STORM. He would like the ALASM interface, and the rest is all
^^^^^^ imhio ray of XAS!
AL> well done.

AL> Sincerely, Alex from FFC COMPUTERS.

Wiz zE BeSt WisHeZ 2 U!
-=JoCkeR/OmEga HaCkErS Grp/1998year=-

AH> ^^^^^^ imhio luche
AH> XASa!

For me it’s better too, but the taste and color...

Monday March 30, 1998 right at 02:09, Denis Dmitriev wrote to Andy Harchenko:

AH>> imhio better than XAS!
DD> he is 512K better for us, but people will be more comfortable at 128K
You didn’t understand me, I told him that i.e. It would be better for ALASM to screw in
the XAS interface.

DD> There would be one like this, with the ZXASM editor, the multi-text content
DD> of ALASM and the power of TASM 4.12 - and... yes, who the hell is
DD> will do it :(
Well, yes, but it will weigh so much, I mean pages? I think that ASM should
eat one page for itself (codes), the rest for the text. And such an ASM, IMHO, will be quite consuming, and by the way, why do you need a super text editor? IMHO, the one in XAS is enough, especially since auto-tabulation + syntax checking,
multiple text is good, but in this case it is again reduced. length
of the main text; about the power, well, I don’t know, again XAS is enough
imho to load the pages and that’s it, the main thing is that the compilation speed is
high, because the more bells and whistles there are, the slower the compiler.
And finally, I think that ASM should be as simplified as possible in terms of the interface,
imho there is no need to make multi-windows, it greatly slows down the process writing, while
you can navigate through the menus, you can get tired. And this increases the length of the code.
It is better here to focus on speed and text size + everything necessary.gadgets.
It’s like I read STORM’s description about its work with numerical constants,
I was blown away, cool, but WHY?! I’m not a sadist and 99% of the time I write normal numbers, and not
#4000+(1+2*(#FE+123/4+7-#7F)+45*2/#1A)/2! I wonder how many kilos of code went into implementing the smart counting algorithm. In short, in my understanding, asm is: simple
text editing (deleting a line/block/character, copying a block, insert/replace mode, rus/lat, transition to the beginning/end of the text, line-by-line scrolling, and so that you can write letters :) + one extra. a page for a different text (you don’t need to :) and of course the fastest possible compiler (the faster the better)
naturally without damage to his brain, but he doesn’t need to be very smart, otherwise you’ll get good at numbers, like in STORM, in a month you’ll look at your source code and go crazy. :) The main thing is that you have everything you need and need, but the rest of the features
you need to look at the memory/speed ratio. And I almost forgot, such asm
should have support for extended memory, otherwise I have a Pent 512, and in XAS the text <=16kb was still the same, and I have tons of free pages, but what’s the point.

P.S.: Damn, sit down to write asm or something, the new principle of storing/compiling
text was invented imho, the speed (if implemented) should be in 2...4 times
faster than XAS. Damn it, FunTop+magazine+study+personal/family matters=NO TIME!

DD> Sbest, Denis.
Dis, what are you doing?

I hit you with my forehead, Andy!

I saw that Thu Apr 02 1998 Andy Harchenko wrote to Denis Dmitriev this:

AH> such asme should have support for extended memory, otherwise I have Pent
AH> 512, and in XAS as it was, the text <=16kb remains the same, but I have a ton of free pages
AH>, but it’s no use.
Well, in ZASM 3.x, even at 128K you have 38 kilos for the text, and besides, the text
is also tokenized - in general, complete rule!

Well, packaged, Andy, packaged!
[Team thief Alos MUST DIE!]

Exactly, but it’s a pity, however... Although one can argue about the degree of sophistication of the rudaktor
. Imho, the simpler the editor, the better, because... the work of editing texts is not slowed down by crawling through different menus.

AH> Well, yes, but it will weigh so much, I mean pages? I believe that ASM
AH> should have one page for itself (codes), the rest for text. A

Do you care? Imho, at 512k it’s not particularly significant - it takes up ASM
1 bank or 2 - there’s still a lot of memory.

AH> such an ASM IMHO will get quite consuming, and by the way, why do you need a super text
AH> editor? Imho, it’s enough that in XAS, especially since
AH> auto-tabulation + syntax checking, multi-text is good, but in
AH> in this case the length of the main text is again reduced; As for
AH> power, well, I don’t know, again XAS is quite enough imho loading on
AH> pages and that’s it, the main thing is that the compilation speed is
AH> high, because the more bells and whistles there are, the slower the compiler. And

Let me disagree with you! It all depends on what kind of program
you are going to write. After all, if, for example, you are going to write an intro of a thousand lines, this is one thing, but if a toy with a source volume of 150-200 kilos, then this is completely different and the required compiler power in these cases will be different. And sometimes for example meIt’s easier to agree to an additional 10 seconds
of compilation than to give up some compiler function.

AH> anyway, I think that ASM should be as simplified as possible in terms of
AH> interface, imho there is no need to create multi-windows, it greatly slows down
AH> the writing process, while you can navigate through the menus, you can get tired.

Absolutely agree!

AH> Yes, and This increases the length of the code. It’s better to focus here on speed
AH> and text size + all the necessary gadgets. It's like I read STORM's
AH> description about his work with numerical constants, I was blown away,
AH> cool, but WHY?! I’m not a sadist and 99% of the time I write normal numbers, not
AH> #4000+(1+2*(#FE+123/4+7-#7F)+45*2/#1A)/2! I wonder how many kilos of code

someone has! As a rule, I use just such expressions ;)
Imho the use of such expressions gives more flexibility to the program than
the use of numerical constants.

AH> went into the implementation of a smart counting algorithm. In short, in my understanding
AH> asm is: simple text editing (deleting a line/block/character,
AH> block copying, insert/replace mode, rus/lat, start/end transition
AH> of text, line-by-line scrolling and so that letters can be written :) + one
AH> extra. a page for a different text (maybe not :) and of course, as fast as possible
AH> a faster compiler (thanthe faster the better) naturally without damage
AH> to his brain, but he doesn’t need to be very smart, otherwise you’ll screw up
AH> numbers, like in STORM, in a month you’ll look at your source material and go crazy
AH>. :) The main thing is that you have everything you need and need, well

Yes? Have you ever tried to get into your source code after a couple of
months? And immediately remembered the values ​​of all the numerical constants? Still, in my opinion
LD HL, SINUS_TABLE looks more clear than LD HL, #A800

AH> other features should be looked at the memory/speed ratio. And I almost
AH> didn’t forget, such ASME should have support for extended memory, otherwise
AH> I have a Pent 512, and in XAS the text <=16kb remains the same, and
AH> I have a crapload of free pages, but it’s no use.
AH> P.S.: Damn, sit down to write asm or something, the new principle
AH> of text storage/compilation was invented imho, the speed (if it
AH> is implemented) should be 2...4 times faster than XAS. Damn it here

Come on, write, I’ve been wanting to see something new for a long time! Maybe I’ll use it too! :)

AH> FunTop+magazine+study+personal/family matters=NO TIME!
~~~~~~ ~~~~~~ ~~~~~ ~~~~~~~~~~~
Exactly! :)

With best wishes, Flying/DR

... -= Digital Reality =-
~~~ Blue Wavev2.12

Friday April 03, 1998 right at 21:05, Eugene Safronov wrote to Andy Harchenko:

AH>> Pent 512, and in XAS the text <=16kb remains the same, but I have
AH>> free pages to no avail.
ES> Well, in ZASM 3.x even on 128K you have 38 kilograms for the text, besides
ES> the text is also tokenized - in general, it’s a complete rule!
This is cool, but how does it behave at 512? Sikoko there is space for text? After all, on a 128
computer, if all the pages except #10 are full, then there’s not much fun in it
too.

Besides, this 40k symbology + multi-window doesn’t suit me.

ES> Well, it’s packed, Andy, it’s packed!

Monday April 06, 1998 right at 00:23, Alexander Grimalovsky wrote to Andy
Harchenko:

AG> it’s different for everyone, but personally, for example, the interface a la ALASM
AG> appeals to me more.
Whoever likes ;)

DD>> will do :(

AG> you can argue with the editor. Imho than before editor, the better, because
AG> the work of editing texts is not slowed down by crawling through different
AG> menus.
Yeah, especially with beer it crawls badly :)

AH>> ASM should eat one page for itself (codes), the rest is under
AH>> text. A

AG> Do you care? Imho at 512k it’s not particularly significant - it takes up
AG> ASM 1 bank or 2 - there’s still a lot of memory.
Yes, I have a Pent512 (I had), but what about 128 kb? After all, not everyone has 512, you also need to take care of those
who have Spec without an upgrade :))

AH>> the compilation speed was high, because the more bells and whistles there are, the slower the compiler. And

AG> source codes are 150-200 kilos, then this is completely different and the required capacity
AG> of the compiler in these cases will be different. And sometimes, for example, it’s easier for me
AG> to agree to an additional 10 seconds
AG> of compilation than to refuse some compiler function.
Hmm, usually you can’t get away with 10 seconds, well, I’m just talking about those functions that
you can live without anyway, for example, course protection :)

AH>>constants, I went nuts, cool, but WHY?! I’m not a sadist and 99% of the time I write
AH>> normal numbers, not #4000+(1+2*(#FE+123/4+7-#7F)+45*2/#1A)/2!
AH>> I wonder how many kilos of code

AG> someone has! As a rule, I use just such
AG> expressions ;) Imho the use of such expressions gives more
AG> flexibility to the program than the use of numeric constants.
Erm, flexibility? What? After all, in the end, the program will contain a specific number, and not that huge expression. You probably wanted to say flexibility in debugging, well
like you substituted #FE instead of #FB, you look and got to where you need to, yes, but in
STORM they have 16 levels of nesting too much, degrees in my opinion are also
counted, something with signs (I didn’t understand).

AH>> you’ll get the hang of numbers, like in STORM, in a month you look at your
AH>> source and you go crazy. :) The main thing is that you have everything you need
AH>> and everything you need, well

AG> Yes? Have you ever tried to get into your source code after
AG> a couple of months? And immediately remembered the values ​​of all the numerical
AG> constants? Still, in my opinion, LD HL,SINUS_TABLE looks more understandable
AG> than LD HL,#A800
Eh-uh, that’s not quite right, I meant addressing not to a label, but to a specific
address, for example, to a screen or to a bar 8). Moreover, you know exactly where you need to go.
Well, in generalI mean, imho few people will use wild arithmetic
expressions, so wouldn’t it be simpler, would it be to simplify the compiler, but the speed would increase.

AH>> the principle of storing/compiling text was invented by imho, the speed (if
AH>> it is implemented) should be 2...4 times faster than XAS. Damn it
AH>> here

AG> Come on, write, I’ve been wanting to see something new for a long time! Maybe I
AG> will use it too! :)
Yeah, as soon as I finish the magazine, I’ll write a demo on FT98, and I’ll sit down for asm. ;)
(the main thing is hope.....)

By the way, will you write a demo again from DR?

AH>> FunTop+magazine+studies+personal/family matters=NO TIME!
AG> ~~~~~~ ~~~~~~ ~~~~~ ~~~~~~~~~~~
AG> Exactly! :)
And it’s spring after all! ;)

AG> With best wishes,
AG> Flying/DR

AH> such an asme should support extended memory, otherwise I have a Pent
AH> 512, and in XAS the text <=16kb remains the same, but I have a hell of a lot of free
AH> pages, but it’s no use.

ES>> besides, the text is also tokenized - in general, complete rulez!
AH> This is cool, but how does it behave on 512? Sikoko there is space for text?
On 256/512/1024/... there is a RAM-Disk, all overlays are stored on it, you can
store program texts, pictures, music. If your program loads any file during assembly, it will be stored on the RAM-Disk, and the next time you assemble it you will not need to load it from disk. Of course, all this is done automatically, although you can turn it off. There is the same amount of space for
_continuous_ text, if you need more, keep additional pieces of
text anywhere (on a RAM-Disk for example) and load them with
INCLUDs when assembling.

AH> After all, on a 128 computer, if all pages except #10 are clogged, then
AH> there is little special
AH> pleasure in it either.
I agree, although 256/512/... is already VERY COOL!

AH> Besides, this 40k symbolism + multi-window doesn’t suit me.
So how much do you need? IMHO, 40 characters are very convenient - 32 is not enough, but 64
your eyes start to hurt :( Although, as far as I know, there is a version of 80 characters per
line using a hardware modification of the screen expansion spec.

AH> Erm, flexibility? What? After all, in the end, the program will contain
AH> a specific number, and not that huge expression. You probably wanted
AH> to say flexibility in debugging, well, like there you substituted #FE #FB
AH> you look and got to where you need to, yes, but in STORM it’s too much
AH> they have 16 levels of nesting, degrees in my opinion are also considered,
AH> something with signs (I didn’t understand).

Well, let’s say two levels of nesting from the point of view of code from 16 differ very little, but that’s not the point. And about the fact that there will be a specific number in the program, you also correctly noted that. But here, for example, is a situation when you need to edit several procedures into memory. How will you set their addresses?
In numbers? What if the size of one of them changes later? Calculate everything again?
And so everything is simple - I wrote an expression and when compiled I got the required number.
If necessary, I can give a few more examples.

AG> This is understandable, but imho 42 characters will not be enough, especially if
AG> you want to attribute a comment.
DM> I completely agree !!!

AG> what? As for functions, now I don’t even know how to live, for example,
AG> without macros and conditional compilation. You may not believe it, but at one time
AG> I rejected 3 or 4 assemblers for myself only because
AG> they did not support parentheses when calculating expressions ;)
DM> You rejected 3 or 4 assemblers because their files
DM> were selected in the menu, and It was not necessary to type them manually :))))))
No, for this reason only a couple :) And the rest because of brackets, or for example
due to the fact that there are 42 characters in a line, or for example a label no more than
7 characters long. I'm quite picky :)

AG> the cooler the compiler, the better, it greatly simplifies the process of not only
AG> writing, but also managing the project, and this is important. I think Slava
AG> Mednonogov will support me.
DM> Both me and I!!!

■ Once on Wed Apr 08 1998, somewhere around 14:34
■ Alexander Grimalovsky wrote(a,o) to Eugene Safronov:

_Skipanned by Malicious Censors_
AG> Well, if you measure the usefulness of ASMA by this parameter, then imho the most
AG> The solution would be ALASM on Pentagon 512k :) But in general - to each his own. I
AG> for example, I think that TASM v4.12 by RST7 is rulez 4ever, and I write everything
AG> only in it!
At one time I also riveted on TASM... I liked it the most!
I also had 3.0 (if my memory serves me correctly) :)
Can you lather me this TASM 4.12 (if not difficult) preferably in
Spectrum format..

... Spectrum Rulezzz 4eva! ... ┌───────┐ WBR, Falcon from MAD GrouP...

AH> there must be support for extended memory, otherwise I have
AH> Pent 512, and in XAS the text <=16kb remains as it was
AH>, but I have a ton of free pages
AH>, but it’s no use.
DD> yes, this is clearly not enough for him.
DD> By the way, about memory - Rst7 was promised to be made in tasm4
DD> ram-disk for the upper memory (not quite the same as in ALASM -
DD> texts will remain 32k in size, there will just be inclusions from the ram).
DD> This is where the rules are buried - both conditional compilation and local labels, and
DD> MACROES!, and... to all this - a disgusting interface :(
^^^^^^^^^^^^^^^^^^^^^^^^
Well, you're in vain! Imho the interface
of TASM4.12 is the most useful of all! And from the point of view vision
editing ASM texts!

Listen, don’t you have this tasm? Or any TASM by RST7 with a version higher than 4.12? ENLiGHT himself spoke with RST7 and he said that he (even then) had TASM version
4.3x ready (x - I don’t remember).

2ALL: People! Who has TASM by RST7 with a version higher than 4.12? Send it in any
way and my gratitude will have no limits (in within reason)!

Well, who knows, tell us how you wrote Binary Love... Otherwise someone is boring...
Please!!!

Don’t forget! Write!
Lyokha.

ES> So how much do you need? IMHO, 40 characters are very convenient - 32 is not enough
ES> and from 64 your eyes start to hurt :( Although, as far as I know, there is a version
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Well, a lot depends on the monitor, its mood and everything is normal. But 40 is clearly
not enough, especially when you write all sorts of messages or comments.

ES> 80 characters per line using hardware modification of the
ES> screen expansion spec.
Yeah, imho, no matter how you set up the monitor, your eyes will definitely fall out soon ;)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Plz, explain to the dark one what this is, then I don’t have it, and in XAS there are no such features.

DD>> With the best, Denis.
AH>> Dis, you or what?
DD> For now I :)
DD> Dismaster/Unicum/X-Project
Yo! Are you going to FT98?

DD> ps: today is a holiday again. or rather three. and both are birthdays...
DD> when they are already over %-)
I sympathize :)

DD> Best wishes, Denis.

AB> Well, who knows, tell me how you wrote Binary Love... Otherwise it’s boring
AB> someone... Please!!!

Buy the cassette - you’ll see! (costs 30r)...

cYa, aR7Y/dR/FW · · · ··· Email: ar...@telecom.nov.ru · · · · · ·

AH>> are considered, something with the signs (I didn’t understand).

AG> will the size of one of them change? Count everything again? And so everything is simple -
AG> wrote an expression and upon compilation received the required number. If necessary,
AG> I can give a few more examples.

Well, I usually do it like this:
LD HL,firstbyt
LD DE,place
LD BC,lastbyt-firstbyt
LDIR

firstbyt LCODE "muzak1"
lastbyt
place EQU #c000

In short the length Muzaka can change, so I calculate its length, similar things happen with
addresses. Imho, super fancy nesting is not needed here.

AH>> will use wild arithmetic expressions, so it’s not
AH>> it would be easier to simplify the compiler, but the speed will increase.

AG> the cooler the compiler, the better, it greatly simplifies the process of not only
AG> writing, but also managing the project, and this is important. I think Slava
AG> Mednonogov will support me.
Heh, heh, again, how can I say that you’re not fed up with the 5-minute compilation
of your big sources?! Let's say you changed a few things in the text that are not significant
and you need to check the work, then you remember with a warm word the fast compiler.
As you can see, the slope/speed ratio also plays a role for large projects, especially
since we have a maximum of 7mhz (well, approximately7)!

Monday April 13, 1998 right at 22:35, Denis Dmitriev wrote to Alexander
Grimalovsky:

AG>> talked to RST7 and he said that he (back then)
AG>> had TASM version ready
AG>> 4.3x (x - I don’t remember).

DD> Wow! I haven’t heard...
DD> How many times have we eaten wine/vodka together, and he, damn it, is always “just
DD> getting ready” ;) Maybe he’s already made a frame there... In general, now he
DD> is finishing the C compiler.
Serious?! On spec?!

DD> Best wishes, Denis.

AH> ^^^^^^^^^^^^^^^^^^^
AH> Damn, maybe there will be that good person who will send me tasm
AH> 4.12 with a description! Or at least explain what CONDITIONAL COMPILATION is!!!!

if ram=1
ld a,a
...
else
ld b,b
...

if we defined ram as 1 then compile ld a,a , if something else then
ld b,b .

by the way, xas has _conditional_compilation_ I specially made it so that I could compile it with one
xas source code for 64 and 42 characters.

ps. commands in xas'e IFZ and IFNZ

SPbZXNet 500:812/03.00 W!7h 7he Be$7 W!$he$ fR0M CREATOR product
Powered by Cyrix 6x86L 200+/16DIMM/S3TrV2 2Mb/SBPro/Q1.6Gb/CDx8/USR33.6

... tHE CREATOR product 1998 (C)

"How BinAry lOve was created" - there the process is shown in action -:)
<- With Best ReGardZ foR U & oNlY...!
ViRtUal/+=SileNce CriOniX=+'98

AH> Buy a cassette - you'll see! (costs 30 rubles)...
And those same pasta comes with it? :)))))

Good luck! Evgeny.

■ The night is shorter than the day... The day will kill me... The world of illusions burns down in it. (C) Aria.

AH> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AH> Well, a lot depends on the monitor, its setting and everything is normal.
So, the fact that you configure it, the 4x8 font matrix will not go anywhere.
And the characters will not become more distinguishable from each other. (By the way, the only
normal, distinguishable 4x8 font that I have ever seen is the font in ZED).

AH> But 40 is clearly not enough, especially when you write all sorts of messages or comments.
Well, 128Kb is sometimes not enough either. :))) It's all a matter of habit...

DD>> local labels, and

AH> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Plz, explain to the dark one what
AH> this is, then I don’t have tasma this, and in XAS there are no such features
AH>.

Local label - a label whose visibility is limited to the body of the procedure,
thus in each procedure you can have
a label with the same name and no conflicts.
Convenient, since you do not need to invent unique names
for each non-significant label.
Conditional compilation - a set of preprocessor directives that allow you to enable
or disable the compilation of specified blocks depending
on the contents of global flags. Thus
by connecting a library block that inside
sets such a flag, and at the beginning checks whether
it is installed, you don’t have to worry that it
will compile for you twice. Or, for example, you can
changing one global flag and get a demo version
, a finished product or something else.

Sincerely
┬ ┬┌┐┬┐ ┐┬┬
╨ґ╨╙ґ╨╙ ╨ ╨

AG>>>> ◊œœ¬›≈, ‘¡À p¡””À¡⁄¡‘ÿ À¡À ÕŸ Binary Love –…”¡Ã… - … ”Õ≈€Œœ … –áÀ¡‘ÿ
AG>>>> »œfi≈‘”—...
DM>>>> Hy 3D ‘œ — ‘≈¬≈ –“≈ƒ¡”‘¡◊ÿ. È ÷…◊œ≈ ◊…ƒ≈œ ‘œ÷≈.
AB>>> H’ À‘œ Œ…‘ÿ, “¡””À¡÷…‘≈, À¡À ◊Ÿ Binary Love –…”¡Ã…... · ‘œ ”À’fiŒœ
AB>>> fiœ -‘œ... ÷Ô‘¡!!!
AH>> Ρ””≈‘’ À’–… - ’◊…ƒ…€ÿ! (30“ ”‘œ…‘)...
EM> · ‘≈ ”¡ÕŸ≈ Õ¡À¡pœŒŸ À Œ≈  –p…á«¡¿‘ÿ”— ? :)))))

Ù≈¬≈ …» ◊ –≈“≈◊¡“≈ŒŒœÕ ◊…ƒ≈ …Ã… ‘œÃÿÀœ ◊ “¡⁄÷≈◊¡ŒŒœÕ?

Spirit^DR [s-no...@usa.net]

Well, plz find out from him! And if suddenly something happens, please tell me, I will be very grateful! From me, give Dima personal greetings and my words about the usefulness of his TASM!

DD> In general, now he is finishing the C compiler.
Wow! Best! For this reason, you need to urgently start studying C!

PS: What compiler do you use?

AH> Heh, heh, again, how can I say, what don’t you get from 5 minutes
AH> compiling your large sources?!
:) Oddly enough, no! :) Although it never reached five minutes (how much volume of source code does it take 5 minutes to compile?!?!), but on average, compiling
some significant project takes me something like a minute :)
Although most of the time is still spent loading from disk.

AH> Let's say I changed a lot
AH> in the text not significant and you need to check the work, this is where you remember
AH> with a warm word fast compiler.
Nope, as a rule (see above) most of the time is consumed by loading from disk, and not compilation! TASM 4.12 is a very fast compiler despite all the bells and whistles,
but it is very inferior in speed to ALASM, because ALASM keeps all sources
in memory, and does not load from disk! Although in light of the latest information about the possible
appearance of a RAM disk in TASM 4.xx..... :)

AH> As you can see, the
AH> ratio also plays a role for large projects, especially since
AH> we have a maximum of 7mhz (well, about 7)!
Nope, still imho the steepness _outweighs_ it is on large projects! Moreover, a well-written compiler does not use any of its fancy features if they are not used in the program! For example, I don't need macros right now - he uses themand it won’t be used => and the speed won’t drop!
As for the processor speed, I personally have 3.5MHz. And Megaball takes more than
a minute to compile. But Oz, for example, writes his Paradise Lost (about 10,000 lines)
in the emulator and its compilation takes about 2-3 seconds.
He has tried more than once or twice to drag me to the emulator, but he still hasn’t succeeded and won’t! And all because even the most beautiful emulsion is not baked!

Wednesday April 15, 1998 right at 10:39, Vladimir Yudin wrote to Andy Harchenko:

VY> A local label is a label whose visibility is limited to the body of the procedure,
VY> so in each procedure you can have
VY> a label with the same name and no conflicts.
VY> Convenient, since you don’t need to invent unique ones names
VY> for each non-material label.

Suppose:

LOOP1 LD A,(HL); first procedure
LD (DE),A
INC HL
INC DE
JR NZ LOOP1

LOOP1 LD A,(DE); second procedure
XOR (HL)
LD (DE),A
DEC D
INC HL
JR NZ LOOP1
LD A,D
OR E
JP NZ,LOOP1; transition to the first procedure

What will the compiler do in this case? If from the second procedure the transition to a
local label is in the first procedure.
And what about JR NZ? After all, in the first procedure you can compile the transition
both forward and backward? How does the compiler separate procedures among themselves?

AH>> will fall out soon ;)
EM> But just like that - they won’t fall out. :) Because first of all
EM> the matrix changes, and therefore the distinguishability of the symbols...
Yeah, especially if you hold them (the eyes) with your fingers or put them on glue, they won’t
fall out. :)))

EM> Good luck! Evgeny.

I’m sitting here, reading, and suddenly I see Denis Dmitriev writes to Andy Harchenko...

Hi Denis!

AH> Plz, explain to the dark one what this is, then I have tasma
AH> I don’t have it, and in XAS there are no such features
AH> Well, I’ll try.
DD> Conditional compilation:
DD> Let's say you have a library of subroutines for outputting a
DD> symbol to the screen. One subprogram for 42x24, another 64x24,

this is how xas are made for 64 and 42 characters

DD> =====================
DD> Well, I told you what I knew.
DD> In addition, conditional compilation can be based on many criteria
DD> (in tasm4.12 has one - compile only on the second pass,
DD> or only on the first), and much more.

and in xas there is

EM> the first thing that changes is
EM> the matrix, and therefore the distinctiveness of the characters...
If you make 64 characters with an 8*8 matrix (thickened font) it will be just a pleasure
to work.

PS: On the question of ZED: we need to make the main mode reader - 64 characters 8*8. But
make it possible to enable at any time the mode of 80 characters 6*4 for pseudo-graphics and tables.

Well, for those who don’t have the modification - only 64 4*8 and 42 6*8. Or maybe only 42 will be enough?
Still, the lines are breaking?

All the best.
With respect, Roman Milukov.

EM>> get away. And the symbols will no longer be distinguishable from each other. (By the way,
AH> They will. If your mixing is not set up, you will have difficulty distinguishing between 6x8.
AH> Everything will merge.
Well, you know... So we will get to “if your brightness and
contrast are not set up well.” :)

AH>>> But 40 is clearly not enough, especially when you write all sorts of mesages or
AH>>> comments.
EM>> Well, sometimes 128Kb is not enough. :))) It's all a matter of habit...
AH> Habit is a habit, but for full-fledged work, 40 characters in a line
AH> is much more inconvenient than 64.
No. :))) I switch to 64 characters only when I work with
IBM BBSs; in all other cases, the most optimal is 42.

AH>> Plz, explain to the dark one what this is, I don’t have tasma
AH>> this, and in XAS features
AH>> there are no such features.
DD>> Well, I’ll try.
DD>> Conditional compilation:
DD>> Let’s say you have a library of subroutines for outputting
DD>> a symbol to screen. One subroutine for 42x24, another 64x24,

EM> first of all, the matrix changes
EM>, and therefore the distinctiveness of the characters...
No, they will just fall out! Today I made this crap, and in the 80
characters mode it’s terribly small, on my pro screen it will be larger.
RM> If you make 64 characters with an 8*8 matrix (thickened font)
RM> it will be just nice
RM> to work.
Here you are right
RM> PS: On the question about ZED: we need to make the main mode of the reader -
There is no need to do anything in ZED, we need to write a new editor and exclusively
on ASMA, and Zed has been a brake so it will remain so!

Sincerely, Andrey.

... The hedgehog is a proud bird: you won’t kick it will fly!

Why suffer - after all, everything has already been invented. Remember IS-DOS, I don’t remember what symbols there were, but you can scroll the screen there!! So you can make a “window” in the text on the entire screen, in which only one letter fits, and scroll (for those especially gifted). For others by choice.

Sincerely, Sergey Kondratov. [ Team Navigator ] [ Orel Team Quake ]
... don't talk nonsense - the enemy is listening!

[...]

RM> Well, those who don’t have improvements - only 64 4*8 and 42 6*8. Or maybe only
42 is enough?
RM> Anyway, the lines are torn?

And what kind of extra work? The one that is supported by Melon?

For example, I have this: 512x192 pixels, monochrome,
Inca color = inverted 2 bit border, paper color = border.
In Melon, stripes go all over the screen %()

If this is what I have, then you can have 85 letters 6x8 (rulez 4ever)
or to speed up the output 64 letters 8x8. I’ll say right away that this is not visible on TV
. And in general it’s _much_ better_ than 256x192. Letters
elongated more than 2 times in height are distinguished much easier
than standard 8x8.

Wi7h be57 Wi5he5, FK0.

-+- SMM version 1.08

DD> Well, let's wait for further versions when the text can handle 512K

xas? IMHO on PC online

DD> take it apart like alasm...
DD> In the meantime, I have alasm4.1 here, I’ll watch it right now :)

well, there’s nothing to do either.

5 > And what kind of modification? The one that Melon
5 > is supported by?
Uh-huh.
5 > For example, I have this: 512x192 pixels, monochrome,
5 > inca color = inverted 2 bit border, paper color =
5 > border.
5 > In Melon, stripes go all over the screen %()
What kind of computer do you have?
5 > If this What I have is 85 letters 6x8 (rulez
5 > 4ever)
Well, it’s still a bit small.

SK> Why suffer - after all, everything has already been invented. Remember IS-DOS, I don’t remember what characters there were, but you can scroll the screen there!! So
SK> you can make a “window” in the text on the entire screen, into which only
SK> one letter fits, and scroll (for the especially gifted).

I understand that you are especially gifted. Imagine that you need
to read a “normal” text document or messages
from several conferences on the Spectrum. From personal experience, the size of this kind of text is from 20 to 2000 kilobytes. In the vast majority of cases
the length of the lines in this text is 60...80 characters.
That is, you will need to read 300...30000 lines. And at _each_
“jump” left and right... In my opinion, a person who considers _this_
the norm is a masochist.

Sincerely, George

SK>> I don’t remember what symbols there were, but you can scroll the screen there!! So
SK>> you can make a full-screen “window” in the text, in which
SK>> only one letter fits, and scroll (for the especially gifted).

GS> I understand that you are especially gifted. Imagine that you need
GS> to read a “normal” text document or messages
GS> from several conferences on the Spectrum. From personal experience, the size of this kind of
GS> text ranges from 20 to 2000 kilobytes. In the vast majority of cases
GS> the length of the lines in this text is 60...80 characters.
GS> That is, you will need to read 300...30000 lines. And for _each_
GS> "jump" left and right... In my opinion, a person who considers _this_
GS> to be the norm is a masochist.
Yes, I forgot to say about automatic line hyphenation ;-)
And the one who tries to distinguish 60..80 characters in a line on a crooked monitor -
really a masochist.

GS> you need to read a “normal” text document or
GS> messages from several conferences on the Spectrum. From personal experience, the size
GS> of this kind of text is from 20 to 2000 kilobytes. In the vast majority of cases, the length of the lines in this text is 60...80
GS> characters. That is, you will need to read 300...30000 lines. And
GS> "jump" left and right at _each_ interval... In my opinion, a person who
GS> considers _this_ to be the norm is a masochist.

The length of lines in the text of letters is not fixed, but is automatically adjusted to
the screen size by the editor using auto-hyphenation. So there is no need to jump
anywhere.
Sincerely
┬ ┬┌┐┬┐ ┐┬┬
╨ґ╨╙ґ╨╙ ╨ ╨

SK> Yes, I forgot to say about automatic line wrapping ;-)

So scrolling, or auto wrapping? I don’t understand anything ;)

If you scroll, then your reading will be limited to a maximum of 10
“normal” pages of text per day. And your fingers will hurt ;)
If automatic transfer - then goodbye to tables, diagrams with pseudo-graphics and other simple joys ;)

SK> And the one who tries to distinguish 60..80 characters in a line on a crooked
SK> monitor is really a masochist.

Here you are very wrong! Do you know the b/w TV "Electronics 404"?
I have one like this. I connected Spectrum (disgusting) and IBM (in
CGA mode - 80*25) to it. So, in the CGA mode the text looked better... Annoying squares merged into readable letters, and long lines, what can I say... Today you simply cannot do without it...
Now I won’t even agree to a character decomposition matrix of less than 14*8,
vision is more expensive than “principles”...

So if someone wants to stay with 32/42 characters per line (or
64 parodies of characters), stay. But don’t drag others along with you...

Sincerely, George

Such problems don’t happen in the Pentagon.
Have you tried selecting a container? There, in the accompanying note to the diagram, something was described.
And, it seems, it will only be on TV. But on the monitor imho - no.

SK> IS-DOS, I don’t remember what
SK> symbols were there, but you can scroll the screen there!! So
I've long been tired of closing the screen back and forth!

SK> you can make a “window” in the text on the entire screen
SK>, in which only one letter fits, and
SK> scroll (for those especially
SK> gifted). For the rest, it's up to you to choose.
Personally, I chose revision. :)

We should have started with this! ;-)
In principle, by combining auto-transfer and scrolling you can get out... If you are too lazy
to modify the computer.

01 May 98 02:55, George Shepelev wrote to Sergey Kondratov:

GS> So scrolling, or auto-transfer? I don’t understand anything ;)
So, one does not interfere with the other.

GS> If you scroll, then your reading will be limited to a maximum of 10
GS> “normal” pages of text per day. And your fingers will hurt ;)
GS> If auto-transfer - then goodbye to tables, diagrams with pseudo-
GS> graphics and other simple joys ;)
Auto-transfer is an optional feature, I wanted it on, I wanted to turn it off.

PS: I see you were bombarded with tables and diagrams on Fido? :)

Sincerely
┬ ┬┌┐┬┐ ┐┬┬
╨╜╨╙╜╨╙ ╨ ╨

RM> Such problems don’t happen in the Pentagon.
RM> Have you tried selecting a container? There, in the accompanying
RM> note to the circuit, something was described.

This is a hybrid circuit.
In the Pentagon for an extended screen, the attribute is set by resistances, and in
Scorpio they did it like in the pros - the value
of the border port determines the attribute screen.
Here they are running ;)

With best wishes, Denis.