Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index

Disclaimer: I have only used Python once to to talk to LO. In fact, I work pretty hard to write all of my "macros" in Basic because support is very consistent across platforms. I cannot comment directly on Python, but, in Basic, I do not need to worry about which interface handles which calls, that level of detail is handled for free.

If I decided to not use Basic, I would evaluate which other language has the best integration, and, I cannot comment on that since I rarely leave Basic. I looked at Python because there was an issue with the Python version for a macro that someone wrote and they were having trouble with integration.

My Primary complaint about Python is that the block structure is directly related to the spacing and I have had that messed with as I moved between machines and operating system. I do not expect that to be a problem if you do not move between machines and if you have full control over the editor that use in terms of how it is configured....... And if you are not pasting code that others have written or from web sites. All of those issues have caused me issues all related to how Python interprets blocks. When I write code in my Python specific editor and I stay on one machine, and I do not integrate code from other places, I have no problems with it. I should note that I work with some people who feel that they must solve every problem with Python.

As for your first language, I do not see a problem with using Python, but I also do not see a problem using Basic. Much depends on your end goal. Especially if you limit external dependencies, Python should run unchanged on most machines with a few caveats.

Why do you want to program? More specifically, what do you want to produce?

What type of programs do you want to write? (GUI, command line, control LO, etc...)

How portable must your code be?

If you want to write a GUI and it will only run on Windows, I think that Visual Studio has a decent environment for development. I spend way more time writing Java and C++ these days, which means that I have not been using Visual Studio lately.

On 2018-07-09 6:20, Tom Davies wrote:
Hi :)
@ Mauricio:  Wow!!!  That was very eloquent! :))  Thanks :)

@ Gordon: Sorry! I had a go with Pascal but got distracted and didn't get very far. It looked a LOT more elegant but i was entrenched in using Basic at the time and couldn't handle the back to basics at that point in time.

@ all: Do you think Python is easy as a 1st language? - or is it better to
start with something else first to ease into it all?

I'm kinda playing around with Scratch a bit and kinda learning Python but
at a very relaxed pace.  Both seem quite good fun now :)

Regards from a Tom :)

On 9 July 2018 at 06:19, gordon cooper <> wrote:

GoTo. One of the curses of Basic, the GoTo.

When used by newcomers (and a few some old hands too) a
Basic program would  soon become an unstructured mess of
GoTo's and a hassle to debug.  One of our Pascal lecturers was
very  anti-Basic and forbade us to use it,  or to even talk about it
in his presence.

Thank you Tom and Jonathon for the memory,

On 09/07/18 15:55, toki wrote:

On 08/07/18 09:04 PM, Tom Davies wrote:

I remember learning one form of basic in the 80s and that was pretty easy

There is a book from the early/mid eighties, that is simply lists the vocabulary of the various dialects of BASIC in use then. IIRC, it was called _The BASIC Book_. It was written specifically for programmers to
port software between the various systems that were available.

Back then, all variants of basic used line numbers, and allowed GoTo.
Today, several variants of BASIC don't use line number, and some
variants don't have GoTo.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.